Quote:
Originally Posted by dgatwood
Careful, there. You're overgeneralizing slightly.
|
Agreed. I'm generalizing.
Quote:
"Avoid" works in lots of rendering engines, but only when used with "inside", not "before" or "after". Avoiding page breaks inside has worked in WebKit since about 2004, so it should work in Kindle KF8 content as well, with a long list of caveats. Unfortunately, many of the ways that people tend to use it run into one or more of those caveats (#3 below in particular).  And, of course, there's no way to get that behavior on MOBI7 readers except to fake it by forcing a page break before the element in question.
|
I freely admit that the caveats alone generally render the thing useless. Hell, #2 alone is a headache, as that can change in an instant.
And yes, #3 is usually the killer, because 99% of the time, the client (bookmaker, etc.) is usually trying to slap a caption with an image, as you've mentioned. The image is usually filling the screen, in width, at least, so...that's DOA.
Quote:
|
AFAIK, even iBooks ignores page-break-after/before:avoid unless they've fixed it in the last year or so and failed to close the canonical bug.
|
Don't know.
Quote:
|
With that said, <SNIP>...but if you're not trying to do this with an auto-sized image, it ought to work for you. Let us know if it doesn't, because that would be an interesting breakage by Amazon (or an edge case, and I'd have to see your actual code to know which).
|
I'll keep my eyes peeled. We have a boatload of complex books going through right now, heavily laden with images, captions, graphics, exhibits, yadda-yadda. I think we've mostly taken to assuming that PBI-avoid doesn't work, for the purposes of what we say to the client or what we promise. I'm also fairly certain that we include it, under the theory that, hey, if it works, great, and if it doesn't, we're no worse off.
Hitch