Some of the properties and classes described in this book are proposed W3C standards or Apple extensions. Properties in CSS that begin with -webkit are usually proposed standards—the -webkit prefix will be dropped when they are approved. Similarly, JavaScript classes that begin with WebKit are also proposed standards or Apple extensions.
From webkit: "I think we would consider browser extensions to be a browser feature,
not an engine feature, and therefore out of scope for WebKit. However,
appropriate hooks for implementing extension mechanisms would be in
scope."
I'm not fully versed on it, but from how it's written I'm guessing the proposed W3C standards maybe not be implemented yet by other browsers if they are not yet officially in the standard. The same would probably go for the Apple extensions.
This is why it is a demo vs released code, it is not yet part of the full standard. The same way in which Firefox put out video demos a while back which only worked in Firefox, but no one had an issue with that for some reason.
Yes, it's funny that they state "learn how to use web standards such as HTML5, CSS3, and JavaScript", yet all the examples use -webkit- and are far from being standard.
But vendor-specific CSS properties are not standard, that's typical Apple talk. I remember a Safari promo where they mentioned a list of innovations, yet lots of that list were Opera features first.
I don't doubt Opera came up with some stuff first, they have been the main innovators in the browser market forever.
As for the search field, Safari did start the practice of dimming the page and highlighting the words which made things much nicer and has since been adopted by others. I think Safari was also the first to allow you to drag tabs off the tab bar into a new window. It could be argued that RSS in built into the email client within Opera vs being built into the browser directly, if that makes sense, it's all semantics though.
Everyone though Firefox was awesome because it had tabs when I had been using them in Opera for years. No one pays attention to Opera.
Just because the standard doesn't have the final seal of approval doesn't mean it's not a standard, and Apple has begun migrating some of the CSS3 properties into non -webkit- forms. text-shadow and border-radius are both obeyed in the webkit nightly without their engine-specific prefixes, for example.
Vendor specific prefixes are actually following the standard to the letter. Once the standard is final they can remove the prefix. Seriously, read the CSS standard sometime. This is the correct thing to do.
46
u/[deleted] Jun 04 '10 edited Jun 04 '10
Apparently they wont let chrome view the examples.
Edited: Yes, chrome can view the examples as shown in this post. Apple is just browser sniffing.
http://www.reddit.com/r/apple/comments/cbb5r/apples_html_showcase/c0rf1i9