EPUB Compat about readium-css HOT 5 CLOSED

The underlying question is whether this must be treated as Readium CSS documentation or in another project entirely (interop)?

At first sight, I believe it could be useful to implementers, especially as it is related to CSS, but I’d be happy to be proven wrong.

from readium-css.

So here comes the first issue of scoping this to Readium CSS: the iBooks.js lib, which is an embedded JS file in fixed-layout books. To clarify, it is not related to iBooks Author widgets, it is something completely different.

The aim of this lib is to provide authors with a set of classes which ibooks.js will use to trigger animations, make elements draggable, play audio, defer events, etc.

As far as I can tell, this lib is self-contained but will fail in Reading Systems that don’t implement navigator.epubReadingSystem.hasFeature('touch-events').

The possibility authors have been using it in the wild (outside iBooks) is unclear though.

from readium-css.

Added ibooks:scroll-axis meta.

My assumption is that scroll mode is tied to the publication’s language and not writing-mode – so it is horizontal for Chinese and Japanese by default. As a consequence, they needed this meta so that authors could override this behavior and set it to vertical if writing-mode is horizontal (which can happen).

But this is just an educated guess.

from readium-css.

Closing this issue since it is now documented.

Authoring libs are out of scope.

from readium-css.

Updated first comment, so that it is aligned with docs, following this EPUB Revision discussion.

from readium-css.