[Turtle91]

Not ignoring, just not giving examples to cover every situation. The simple example I gave shows the concept of using css properties and techniques to code for different devices. There are other techniques, such as the multiple css sheets to cover for ADE’s non-compliant issues, or devices that gag on a particular sheet. Other techniques that have been addressed on other threads discuss using techniques like @media queries or @supports queries or even JavaScript to link the appropriate css file at runtime based on the capabilities of the device.

There are ways to overcome most of these issues. However, as DNSB mentioned, if your device is soooo borked up that it can barely turn itself on, let alone meet the ePub2 specification, then there really isn’t a need to code for them anymore. Keeping coders from using the current spec because someone, somewhere, might have a Frankenstein device that can’t run it is not logical.

Besides, my biggest point here is keeping the MR readers from giving up on finding a solution just because Jon doesn’t think anything exists beyond ePub2… there are solutions to 98.9% of these issues…