multifariam.net

So, when Jobs said on stage that “if it renders in Safari, it will render on the iPhone”, he was just kidding.

In addition to various JavaScript rendering glitches (e.g., side scrolling), it seems that the iPhone cannot pass acid2 .

This is odd, because WebKit has passed acid2 since 2005 .

If you are looking for the iPhone’s WebKit version, it identifies itself as:

mozilla/5.0 (iphone….gecko) version/3.0 mobile/safari/419.3
applewebkit version 420
Thanks to intelinsanex

For reference, Safari 3.0.2 beta is:

Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en)
AppleWebKit/522.11 (KHTML, like Gecko) Version/3.0.2 Safari/522.12

While the latest Safari 2.0.4 is AppleWebKit 419.2.1, Safari/419.3. I’d like to pull the full user agent string, but Safari 3 beta overwrote my stable copy of WebKit used by Safari 2. Thanks, Apple.

Safari mobile, while “between Safari 2 and 3”, is far closer to v. 2. It is also a very heavily modified build that breaks who knows what else. There’s no bug list yet, according to WebKit developers.

From an IRC chat session in #WebKit last week:

AnObfuscator: On that note, is there a list of known bugs between Safari/OSX/Win and Safari/iPhone — specifically, CSS rendering glitches?
othermaciej: AnObfuscator: we don’t have an exhaustive list, no
othermaciej: AnObfuscator: we are working to bring all the versions of Safari closer together in rendering
AnObfuscator: othermaciej: Cool. is that a webkit project? Is there somewhere specific in the bugtracker I can follow along, perform tests, etc?
AnObfuscator: othermaciej: I noticed the acid2 glitch, and that kinda surprised me
pewtermoose: othermaciej: are all the iPhone changes in svn or is that coming (or at all)?
othermaciej: pewtermoose: they are not in SVN currently
othermaciej: we do expect the trees to be synced in time

So, the bugs exist. They are known. They are not provided to developers. The code that contains them is not yet available to developers (thanks, Apple, for violating the LGPL).

Does anyone out there still believe that Apple takes its “pretty sweet solution” seriously, as a development platform?