3 ms·

I think this is entirely different. Apple is using CSS3 to generate compliant HTML files for their application interface (see the link to Will Norris' post, whi

by martey 17y ago

I think this is entirely different. Apple is using CSS3 to generate compliant HTML files for their application interface (see the link to Will Norris' post, which includes a link to a HTML file you can view in any browser). I think this is interesting not simply because Apple moved the iTunes Music Store interface from proprietary XML to HTML, but because this might allow for (unauthorized) third party iTMS interfaces, similar to pymusique/SharpMusique: http://en.wikipedia.org/wiki/SharpMusique http://en.wikipedia.org/wiki/SharpMusique

btn 17y ago
using CSS3 to generate compliant HTML files A significant chunk of the CSS is vendor-specific. Similarly, the HTML contains Apple-only attributes and segments designed to only be interpreted by iTunes. Neither the HTML nor CSS is "compliant" (ie. validating). to a HTML file you can view in any browser Except it's completely broken in anything but WebKit-based browsers, and isn't functional outside of iTunes. They've moved from proprietary XML to proprietary HTML. This doesn't open up any new doors for third-parties; it's just a convenience for the people at Apple to design new content for the store.
- tewks 17y ago
  This design choice is significant because most of these properties, or their equivalents, will be or are already implemented in several CSS3 rendering engines: it's a great demonstration of what we will soon be able to do with cross-browser support. The fact that IE or browser x can't browse the iTunes store is less important than some other tactics on Apple's part such as lack of non Apple device support...
- rimantas 17y ago
  They are using http://www.apple.com/itms/ http://www.apple.com/itms/ namespace, not the w3c one. It does not make much sense for XHTML1.1, but trying to validate their markup is not making any more sense either.

3 ms·

I think this is entirely different. Apple is using CSS3 to generate compliant HTML files for their application interface (see the link to Will Norris' post, whi

by martey 17y ago

btn 17y ago
using CSS3 to generate compliant HTML files A significant chunk of the CSS is vendor-specific. Similarly, the HTML contains Apple-only attributes and segments designed to only be interpreted by iTunes. Neither the HTML nor CSS is "compliant" (ie. validating). to a HTML file you can view in any browser Except it's completely broken in anything but WebKit-based browsers, and isn't functional outside of iTunes. They've moved from proprietary XML to proprietary HTML. This doesn't open up any new doors for third-parties; it's just a convenience for the people at Apple to design new content for the store.
- tewks 17y ago
  This design choice is significant because most of these properties, or their equivalents, will be or are already implemented in several CSS3 rendering engines: it's a great demonstration of what we will soon be able to do with cross-browser support. The fact that IE or browser x can't browse the iTunes store is less important than some other tactics on Apple's part such as lack of non Apple device support...
- rimantas 17y ago
  They are using http://www.apple.com/itms/ http://www.apple.com/itms/ namespace, not the w3c one. It does not make much sense for XHTML1.1, but trying to validate their markup is not making any more sense either.