View Single Post
Old 11-29-2020, 01:19 PM   #5
thiago.eec
Wizard
thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.
 
Posts: 1,217
Karma: 1419583
Join Date: Dec 2016
Location: Goiânia - Brazil
Device: iPad, Kindle Paperwhite, Kindle Oasis
Quote:
Originally Posted by jackie_w View Post
Should/shouldn't isn't really the issue. The fact is some publishers *do* produce this nonsense CSS.

I'd quite like calibre Check Book to flag this as a Warning if it was easy to do.
Exactly. I'm talking about books I bought. I would never do such a thing.

Quote:
Originally Posted by kovidgoyal View Post
class names in css selectors are case insensitive.
Well, there is something odd: the Editor treats CSS selectors as case-sensitive (as Sigil and ADE), but the Viewer treats them as case-insensitive (as Azardi and Readium).

Also, digging a little bit, I found this:

1) CSS selectors are indeed case-insensitive, but...
2) HTML class names are case-sensitive, according to the specs* (except in quirks mode, for HTML5).

* https://www.w3.org/TR/REC-html40/str...l.html#h-7.5.2
https://www.w3.org/TR/html50/disable...se-sensitivity

Does the viewer and the preview panel (editor) use both the exact same version of Chrome?

Last edited by thiago.eec; 11-30-2020 at 03:42 AM. Reason: typo
thiago.eec is offline   Reply With Quote