Apple & HTML5

Post by pornel » Fri, Jun 04, 2010, 7:10 PM UTC

statictype wrote: post #126

mikedouglas wrote: post #40

Earlier quoted context omitted.

Actually, transform is in the CSS3 working spec[0]. Until the standard reaches the "Candidate Recommendation" stage, the W3C encourages browser vendors to use prefixes (-webkit, -moz, etc). DXImageTransform.Microsoft.Alpha, on the other hand, wouldn't be part of CSS3, and uses its own specific syntax. [0]: http://www.w3.org/TR/css3-3d-transforms/#transform-property

Is there any technical reason why using webkit's browser specific css attribute and firefox's browser specific css attribute is any better than using IE's browser specific css attribute?

Post by jolan » Sat, Jun 05, 2010, 1:32 AM UTC

alanh wrote: post #66

tmsh wrote: post #56

Earlier quoted context omitted.

The issue may be, however, that the standards committees for HTML5 haven't defined how different implementations of these standards are supposed to play together. And the question is: does Apple have the right to define how HTML5 should be handled cross-browser? (In this case, by very simply denying all non-Safari browsers -- at least via that link -- the developer links work -- kind of.) In all fairness, I think the…

I’m sorry, but I am not sure what you are saying. Web standards circles agree that "browser sniffing" as opposed to "feature detection" is kind of evil. (See http://modernizr.com for one way to do it right.) This, however, is a very special case, where the whole point is showing what ones specific browser can do. Generally, the user's browser is irrelevant to the point of a website, and supporting as many browsers as…

Post by steveklabnik » Sat, Jun 05, 2010, 5:46 AM UTC

buster wrote: post #38

ellyagg wrote: post #27

Earlier quoted context omitted.

> This sets a very poor example for Apple supporting standards. Can you, or any of the dozens of upvoters, explain the logic behind that criticism? It literally seems to make no sense to me, so I must be missing something. The page talks about emerging web standards and talks about Safari and Apple's support for them. It mentions that not all browsers support all of the latest standards, and then it gives examples of…

It's no standard because apple developers extended Webkit with some additional tags but noone else. That's what makes it so sad. Even more sad is that they misuse the words HTML, CSS3, JS and standard to convince you of the oh-so-open world of Apple. MS did that for years and every web developer pays for that today. But somehow now it's ok.. You don't see how having to install Safari for Apples vision of the internet…

Post by loewenskind » Mon, Jun 07, 2010, 7:28 AM UTC

smackfu wrote: post #106

loewenskind wrote: post #83

Earlier quoted context omitted.

Did you read the thread? At least 3 people (at the time of this reading) have done it. You have to change the user agent setting.

How can you say they aren't blocking Chrome if you need to say you aren't Chrome to run it?