You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2020. It is now read-only.
Just recording my thoughts but a handful of existing features in other Reading Apps came to my mind when closing the UX issue in Readium CSS:
opening table in a dedicated web view/modal when double-clicking/double-tapping it;
opening figure/img in a dedicated web view/modal when double-clicking/double-tapping and/or pinch-to-zooming – I’ve never quite understood why the figcaption is ignored when it is available though;
when handling links, there’s also linear="no" documents;
it’s not uncommon apps are also using pinch to zoom to change the font-size.
What do we want to do for those ones, and possibly others I can’t recall right now?
BTW is highlighting implied?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just recording my thoughts but a handful of existing features in other Reading Apps came to my mind when closing the UX issue in Readium CSS:
table
in a dedicated web view/modal when double-clicking/double-tapping it;figure/img
in a dedicated web view/modal when double-clicking/double-tapping and/or pinch-to-zooming – I’ve never quite understood why thefigcaption
is ignored when it is available though;linear="no"
documents;What do we want to do for those ones, and possibly others I can’t recall right now?
BTW is highlighting implied?
The text was updated successfully, but these errors were encountered: