Thread: EPUB 3.3 BECOMES A W3C RECOMMENDATION
View Single Post
Old 06-01-2023, 02:20 PM   #49
graycyn
Wizard
graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.graycyn ought to be getting tired of karma fortunes by now.
 
Posts: 1,591
Karma: 11722446
Join Date: Aug 2010
Location: NE Oregon
Device: Kobo Sage, Pocketbook Era, Kobo Forma, Kindle Oasis 2
Talking
Quote:
Originally Posted by JSWolf View Post
That is incorrect. ADE 2.0.1 will not work with <figure> no matter what you do with it in CSS. It needs to be a <div>

All of those "commands" won't work. That's the problem. ePub 3 could be more backwards compatible with ePub 2 without removing any of the functionality.

So no, they won't work with legacy reading system that are not based on an up-to-date enough webkit.
Are you trying to use them in an epub2 or something? That might not work, I don't know, haven't tried any such thing.

<figure> (and the other HTML5 block elements) work just fine in epub3 on my ADE 2.0.1.78765 install! On my PC, on my Kobo, and on my Sony PRS-T2 for that matter. Oh, also in the Nook android app.

I'm digitizing (slowly) some of my rare books to epub so that I can re-read them as my eyes age, and many are illustrated, so I use <figure> and <figcaption> quite frequently.
graycyn is offline   Reply With Quote