Daniel Weck
Daniel Weck
Is this by design? From the user's perspective, the inconsistency in the reading experience compared with EPUB publications makes this seem like a bug.

Related issue: https://github.com/readium/readium-desktop/issues/326 We need to better support schemes such as "Problem Details JSON" (RFC7807) for server "error" responses (to be precise: response bodies associated with non-`2xx` status codes). The...
Currently fails. See: https://github.com/readium/readium-desktop/issues/97#issuecomment-618898849
Same React technique as modal dialog and popup menu, in order to set aria-hidden on the principal app viewport (screen reader), and ensure consistency between keyboard focus lock (cycle within...
...current locator does not report nearest preceding page break, and no text rendering. This is because the DTBOOK-to-XHTML conversion actually starts from SMIL (not DTBOOK) with `class="pagenum"` attributes, but no...
We already support multiline / line break matching with collapsing of whitespace / DOM space-tab identation. However, we need to implement string normalization of ligatures / unicode pairs, diacritics /...
Follow-up to https://github.com/edrlab/thorium-reader/issues/987
 
For EPUB3 Media Overlays users have the option to turn on "skippability", this should apply to TTS as well.