Quote:
Originally Posted by troymc
Both of these appear to work fine in ADE (Sony/Nook) & webkit (Sigil/Calibre) readers. But don't ask why since I thought inline-block was not part of the spec.
|
Indeed, my original method (see up in this thread) was similar to yours - just an 'inline-block' paragraph inside a block div. But inline-block is not in the standard - I looked it up. It may work now, but a firmware upgrade on a reader might make it stop working. That's why I came up with the convoluted 'inline-table' method. Personally, I'd prefer to use inline-block but I'm trying to offer a standards-compliant method that will hopefully continue to work as these machines mature and become more strict about the standard.
I think inline-block works in Sigil and Calibre because they implement the full CSS spec instead of the subset that is EPUB. I've stopped using them for proofing because of that unreliability (although I still use Sigil for editing). I have no idea why it works in ADE - ADE is missing a lot of other CSS (and HTML) features, so it doesn't make sense that it would implement this one.
The standard supports the following visual display models: none, inline, block, run-in, table, inline-table, table-row-group, table-header-group, table-footer-group, table-column-group, table-row, table-column, table-cell, table-caption, inherit, oeb-page-head, and oeb-page-foot.
Reference:
http://www.idpf.org/2007/ops/OPS_2.0...tml#Section3.3