Skip to main content

Bug Tracker

Side navigation

#13597 closed bug (notabug)

Opened March 11, 2013 09:29PM UTC

Closed March 11, 2013 10:01PM UTC

Early WebKit Build lacking trim support

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 2.0b2
Keywords: Cc:
Blocked by: Blocking:

When attempting to use jQuery 2.0.0b2 (and b1) on an internal WebKit browser on an embedded device, there is an issue where String.trim() is not supported natively.

''TypeError: Result of expression core_trim [undefined] is not an object.''

I know little about our webkit build other than the fact that the user agent reports version 525 (which is useless, I know but the only 'firm' number I have. Of course, our acid scores are much higher than what 525 would seem to indicate so I doubly doubt that number is useful at all)

Is this something that was overlooked, or is our build of webkit too old to support in the 2.0 branch? Unfortunately updating WebKit is not an easy task since we are on an embedded device. I was able to work-around using the compatibity provided here:

Attachments (0)
Change History (3)

Changed March 11, 2013 09:40PM UTC by dmethvin comment:1

owner: →
status: newpending

How old is your device? If it's not a common situation then I think our position should be that you should just use 1.9 there.

Changed March 11, 2013 09:43PM UTC by anonymous comment:2

Its a device on a very recent broadcom chipset, with a browser core delivered by broadcom based on webkit.

Since its an embedded device, the smaller the files the better which is why I want to use 2.0 instead, but as I said if its not an oversight I can work around it.

If this is not seen on the 2.3 android devices then I think it is very safe to say my webkit build is just too old.

Changed March 11, 2013 10:01PM UTC by dmethvin comment:3

resolution: → notabug
status: pendingclosed

If you want to give 2.0 a go, just create your own shim of jQuery.trim() and see how much further that gets you. But in general even 2.0 isn't designed for an arbitrarily old WebKit so we wouldn't consider this to be a bug. If it was Android 2.3 then there are enough of those for us to be worried.