121–130 of 137 posts
Neat idea, very poor implementation. If you try to view the examples in Google Chrome, you'll get a notice that you have to download Safari ( http://skitch.com/bradgessler/dgw7p/apple-html5 ) This sets a very poor example for Apple supporting standards.
Earlier quoted context omitted.
What is the purpose of showing demos that work only on Safari? How can one call this a standard? Standards should work everywhere IMO. One of the many criterion I use to define a standard is that it is widely available. Right now, Flash is more a standard than HTML5 according to this criterion. Jobs is doing what Gates was doing - locking everyone on his platform. I don't know the stats but the Safari browser share i…
Since when does a "standard" mean that it magically works across all browsers. Is HTML5 less of a "standard" because Microsoft is too lazy to implement it properly in their browser?
Earlier quoted context omitted.
What is the purpose of showing demos that work only on Safari? How can one call this a standard? Standards should work everywhere IMO. One of the many criterion I use to define a standard is that it is widely available. Right now, Flash is more a standard than HTML5 according to this criterion. Jobs is doing what Gates was doing - locking everyone on his platform. I don't know the stats but the Safari browser share i…
Nobody cares about your definition of standard. Standards should work everywhere IMO By this definition we hardly have any standards. Say hello to IE6.
Earlier quoted context omitted.
Upvoted. You are correct. HTML5 is not yet even approved W3C candidate recommendation. To be more accurate Apple should have said that it is committed in implementing HTML5 standard, not that it has done it, because at the moment HTML5 is not ready. From Wikipedia: "Ian Hickson, editor of the HTML5 specification, expects the specification to reach the W3C Candidate Recommendation stage during 2012, and W3C Recommenda…
2022? Then those guys move too slow to be useful. Good on Jobs for trying to force it to move at a more reasonable pace. There is no reason to wait so long.
Earlier quoted context omitted.
I think the accusing party has to explain why something is hypocritical and propaganda.
Ah okay. Well for starters, claiming they are using open standards and then trying to block based on user-agent for only Safari.
Earlier quoted context omitted.
A poignant example is all of the non-standard -webkit CSS extensions Apple uses for the Gallery demo ( http://www.apple.com/html5/showcase/gallery/ ): #gallery-demo .grid2d figure:nth-child(5) { -webkit-transform: translateX(-241px) translateY(-3px) scale(.45) translateZ(1000px);} If you accept -webkit CSS extensions as a standard, then Internet Explorer has supported the CSS opacity attribute for years: filter: prog…
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
Earlier quoted context omitted.
What is the purpose of showing demos that work only on Safari? How can one call this a standard? Standards should work everywhere IMO. One of the many criterion I use to define a standard is that it is widely available. Right now, Flash is more a standard than HTML5 according to this criterion. Jobs is doing what Gates was doing - locking everyone on his platform. I don't know the stats but the Safari browser share i…
The point probably being that these features are specified in the standard, but aren't implemented everywhere yet. This isn't lock in, because other browsers will presumably implement them soon(tm).
In reality, all of the CSS transforms and effects (and plenty of other Safari features) were created by Apple without input from any of the other browser vendors or standards bodies. Some of those things have been picked up, some haven't. I actually think this is the right way to do things, and I don't want to give off the impression that I don't appreciate what the Safari team has spent the last few years doing, but I'm also not wild about letting Apple distort the picture for the sake of scoring PR points against flash (which is what this website is all about).
This is meant as inspiration, as an eye-opener, a PR move, and a gift to web developers & designers. It does use emerging web standards . Just because some of them are not reliable everywhere does not discount that it’s all to be found in W3C and WHATWG draft specs. Note the HTML itself: They’re using , , . It’s really HTML5. (Remember, we consider things “standard” even before IE supports them.) This is not meant as…
Earlier quoted context omitted.
Nobody cares about your definition of standard. Standards should work everywhere IMO By this definition we hardly have any standards. Say hello to IE6.
IE6 was the standard. It is not longer the standard because it was written in 2001. Bash IE6 all you like, normally I would join in but make sure its a valid point.
I am a member of WHATWG mailing list so I can see how standards are born, and this level of misunderstanding about web standards in general and HTML5 in particular really saddens me.
Earlier quoted context omitted.
Nope. Google uses a ton of WebKit code, submits a lot of code back into WebKit proper, but they're doing their own stuff too. IIRC they wanted to have GPU acceleration for 3D CSS which apparently WebKit proper doesn't offer at this point or Google thinks they can do it better. You can't safely assume all WebKit based browsers are going to be equal.
WebKit proper doesn't offer at this point I've got a radar open with Apple about Safari's performance (that I know WebKit people have at the very least seen ) that essentially boils down to this reason.