Quote:
Originally Posted by Hitch
Have you given any thought to fallback coding? For the snapblock use for ET?
|
I'm assuming the fallback is its usual functionality. You'll get the big gap, just like Post #1.
(There hasn't been extensive testing though... interesting how this exact use-case popped up just a few weeks after Amazon even announced the snap-block code is now "supported", so nobody has really tested the boundaries yet.)
Quote:
Originally Posted by bo4568
Code below doesn't work? It didn't split it any single time:
|
You have to be careful with <figure> + <figcaption>. That's HTML5, and functionality across older devices isn't guaranteed.
And as you can see here, using bleeding edge code (like the new snap-block floats) probably doesn't mix too well.
Wonder if Post #6's caption-not-floating bug will occur if you wrap Post #6 in <div>s instead of using <figure>+<ficaption>?
* * *
And on the "Image+Captions stuck together"... there are dozens of examples on MobileRead over the years, discussing all the pros/cons, and various different methods/reasonings on how to work around this.
Most can be found by searching:
Code:
RbnJrg SVG caption site:mobileread.com
in your search engine.
It also depends if you're creating EPUB2/EPUB3, MOBI/KF8/KFX, or personal/for the MobileRead library, etc.