

Moreover, this format is using interactive widgets which are managed at the Reading System level (the EPUB file contains with a type of application/x-ibooks+widget and custom data-attributes for styling). ibooks-layout-hint, -ibooks-list-text-indent, -ibooks-strikethru-type, -ibooks-strikethru-width, -ibooks-underline-type, -ibooks-underline-width, -ibooks-stroke, -ibooks-popover-background, and -ibooks-popover-shadow) and the Tab Stops for CSS. It is probably used to trigger another rendering engine which supports very specific -ibooks- prefixed CSS properties (i.e. This meta is automatically added to EPUB3 files generated with iBooks Author. Since 2012, Amazon has been providing authors with non-standard media queries so that they specific styles can be declared for the old format (Mobi7) and the latest ones (KF8 and above). It will then be a lot more difficult to make progress happen. The hard truth is that if authors feel this is not well-supported, they won’t use it. It indeed is one of the very few mechanisms allowing authors to do progressive enhancement (layout, typography, etc.), especially as it helps get around older Reading Systems which have no concept of fault tolerance, and will consequently ignore the entire stylesheet if they encounter some of those more modern properties. It is critical for the advancement of modern CSS that implementers try their best at supporting this rule, especially when pre-processing EPUB files before distribution. CSS at-rule lets authors specify declarations that depend on a browser’s support for one or more specific CSS features.
