View Single Post
Old 09-12-2014, 01:34 AM   #16
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by odedta View Post
@JSWolf: That's a CSS3 rule isn't it?
Correct me if i'm wrong, devices that don't support CSS3 will ignore the entire file if it "has errors" such as font-face rules or media queries. So, it's best practice to put them in a separate stylesheet.
@font-face is in CSS 2.0 and CSS 3.0, was removed from CSS 2.1 because no browsers supported it, and is AFAIK the only part of the EPUB 2 spec that explicitly references CSS 2.0 instead of 2.1.

With that said, even if it weren't, the CSS specification (CSS 2.1 section 4.2) explicitly defines the rules for parsing declarations, and how to handle declarations that you can't interpret. Those rules are there precisely to ensure forward compatibility in situations like this.

More to the point, any reader that ignores an entire file because it "has errors" is egregiously violating the CSS specification, and should be considered defective by design.

That means you, Adobe.
dgatwood is offline   Reply With Quote