Apple, It's Not A Standard If It Only Works In Your Browser, And On The Mac

Apple today posted an interesting new HTML 5 and Web Standards section to its web site, a counterpoint of sorts to Microsoft's Internet Explorer 9 Test Drive site (and yet another assault on Adobe Flash). There's just one problem: Unlike the Microsoft effort, Apple's site only works properly in its own Safari web browser, which undercuts the point the company is try to make. Safari, after all, is used by less than 5 percent of web browser users worldwide.

There's another issue here, of course. This site also proves my contention that WebKit is a lie. That is, Apple previously explained that WebKit-based browsers were a de facto standard because this rendering engine is used by both Safari and Google Chrome, and that these browsers represented most of all mobile web traffic. My point is that there is no such thing as a single WebKit because each browser implements different WebKit versions and render web pages differently.

If you access the individual demos from Apple's Safari Dev Center with Chrome, instead of via the main site, you can in fact view them. And when you do, you discover that the experience is a subtly different in each browser. In Windows.

As noted above, this is all very subtle. And none of the example here would impact the functionality of a site. Things are just rendered differently.

Look beyond Windows, however, and the experience is even more different. On the video demo for example, Mac users on Safari get a Mask control while Windows users don't, in any browser. And some demos don't work at all on Safari for Windows. When Microsoft talks about "same markup," this is what they mean. The same HTML code should render identically in each browser. It's not enough to "support" various HTML 5 features. It should look and work the same, everywhere.

The thing that's odd about all this is that I do believe that HTML 5 is the future of the web, and that proprietary technologies like Flash will become less and less necessary as we move forward. But these Apple demos simply prove that that future is still a ways off, and certainly isn't here today.

Discuss this Article 15

meason
on Jun 4, 2010

It's probably just another back door way for apple to get windows users to download safari so they can say they increased their installed base.

AugieD369
on Jun 4, 2010

I agree with you there Paul.  The point of having web standards is to ensure web sites are rendered the same across all web browsers and in the case of Windows, the same across all operating systems and devices.  HTML5 is not yet finalized so there is time for all web browsers to make adjustments to render the same. Consistant rendering is what Microsoft wants and why they are taking their time implementing HTML5.  I have been messing with the IE9 dev preview and I can't wait to see how IE9 will compare to "Webkits" once we have a fully working IE9 beta.

yoshipod
on Jun 4, 2010

"Apple, It's Not A Standard If It Only Works In Your Browser, And On The Mac"

That is a very misleading title.

If it is a published standard, then it is a standard, no matter where is runs or does not run. Just because other vendors / platforms have not implemented the features in Apple's demos does not mean they are not a standard.

If you want to talk about the fact that HTML5 and CSS3 are not finalized and ratified and therefore, not truly a standard, then you certainly have a point.   Otherwise, this seems like the typical sour grapes argument.  

On a related note, If Microsoft was really interested in code rendering identically they should start first with Office.  I can't count the number of problems we see here on Powerpoint & Word when switching between Macs and Windows machines.

Dipsh t Admin
on Jun 4, 2010

Interesting too that they say these demos are "best viewed" in "Safari iPhone OS, Mac OS X, Windows", which implies that they are viewable in other browsers, but the best experience in Safari.  That is not the case.

meeyou
on Jun 4, 2010

Worked fine in my Mac Chrome browser. I had heard the same re: Safari but gave it a go anyway... and voila,...

Maybe Safari is, even worse, just a windows thing! Gotta love Apple :(

clindhartsen
on Jun 4, 2010

*richmanvoice* Oh, but Paul, you're talking about supporting those little peasants who use Windows, all those poor billions of people. Why would developers care about them, would they really enjoy the art of HTML5 pages that work with the world's premier browser? *endrichmandsvoice*

Seriously though, this seems like Apple doing what Apple does: Pushing their own brands like crazy. The different now is that they drape it in the word "standard"

planetarian
on Jun 4, 2010

yoshipod: It really comes down to the notion that different products within microsoft are worked on by different teams -- which don't generally communicate with each other that well. if the IE team is the left hand, then the Office team is the right, and neither knows what each other is doing -- and both have different goals. What it comes down to is that the IE team has decided they're going to put effort into 'same markup' while the Office team doesn't have it as a priority.

For that matter, I'm pretty sure that Office has different teams for Windows and Mac, as well...

Keleko
on Jun 4, 2010

They coded it to be known working in Safari.  They probably didn't want to spend the time to do multibowser support.  This sounds a lot like IE only websites.  Shame for not doing that, but it isn't like it hasn't been done before with other browser versions.

Waethorn
on Jun 4, 2010

"If it is a published standard, then it is a standard, no matter where is runs or does not run. Just because other vendors / platforms have not implemented the features in Apple's demos does not mean they are not a standard.

If you want to talk about the fact that HTML5 and CSS3 are not finalized and ratified and therefore, not truly a standard, then you certainly have a point.   Otherwise, this seems like the typical sour grapes argument."

Paul has a point which you actually prove:  HTML5 is neither a published standard, nor is it the de facto standard used by the majority of users (that title belongs to IE for HTML, and Flash for interactivity).

In any case, I think I'd rather code towards IE9 for standards support:

samples.msdn.microsoft.com/ietestcenter

jeffsters
on Jun 4, 2010

The reason was they couldn't be sure how other browsers would render the pages so it was restricted to WebKit with the expectation that it would provide the best experience.  What I find amusing is that after all these years some don't get, or pretend they don't, that Apple is ALL ABOUT the user experience and will do things like this, like restricting apps, focus on a single cell provider, etc., if it means providing a best in class user experience. Apple doesn't want, or need to be, the biggest (remember iPhone has only about 15% share), it only needs to be what it feels is the best.  If you don't like it, you're free to let your wallet do the talking!

BrandanL
on Jun 4, 2010

@Paul

"It should look and work the same, everywhere."

Like the JPEG says, this is just a pipe dream (tee hee). The best we will ever get is "really similar." Native media player controls, typography, things like that are going to render subtly differently across browsers, and that's okay!

dowebsitesneedtolookexactlythesameineverybrowser.com

I agree that Apple's demo was a little boneheaded. It's definitely a marketing piece, not really meant to stand up to developer scrutiny. But why not spend the time on proper feature sniffing when you're supposedly one of the industry's biggest supporters of forward-thinking web development?

felipe.alfaro
on Jun 4, 2010
The only differences that I see are the fonts look a little bit differently. Did you compare the WebKit versions used by Chrome and Safari?
duanewatson
on Jun 4, 2010

Yoshipod:

The title is not misleading at all; that's what Apple's doing here: saying "Look at how we implement standards (but you need our browser to do it)."  If their point is openness, then this malarkey about needing to download Safari would not be necessary.

chuckb84
on Jun 4, 2010

Given the sad record that Microsoft has on "standards" in IE, this post definitely has a pot calling the kettle black ring to it.

However....

Standards are important, arguably the most important thing in the computer software biz, because it keeps a single company from getting  a de facto lockin. Think .doc, .xls, .ppt formats, etc. Microsoft has honed this to a fine art.

So, the Apple demo page proves that not all browsers implement HTML5. This is news?

And the "Webkit is a lie" is really overdone. There are IEE standards on, say, floating point arithmetic, and yet (gasp!) not all computers perform the same series of 1 billion operations to give the exact same result!

That does not undercut the value or purpose of the IEE standard, and the --minor--variations in a rendering engine do not undercut the utility of HTML5.

robertsjoe
on Jun 4, 2010
The future is WebKit. It sure as he'll isn't IE!

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• 120 Technical
Sessions
• Networking with Peers
• Expert Speakers


Come See Paul Thurrott & Mary Jo Foley in Person!

Register Now

Office 365 InfoCenter

Get the latest insight and info from Paul

Read Now!

What I Use