Skip to content
This repository was archived by the owner on May 7, 2025. It is now read-only.
This repository was archived by the owner on May 7, 2025. It is now read-only.

Nav problem with page-progression-direction=rtl(cloud reader 2.28.0-alpha) #661

Open
@toshiakikoike

Description

@toshiakikoike

This issue is a Bug

Expected Behaviour

From Navigation, link to valid fragment identifier.

Observed behaviour

Instead, Readium does not link to valid fragment identifier, when EPUB's page-progression-direction="rtl"

Steps to reproduce

  1. First, open the test file by readium-js-viewer : cloud-reader
  2. Then open navigation
  3. Click, Chapter2, Chapter3, then jump far backward from valid fragment.

Test file(s)

https://github.com/toshiakikoike/epub_file/blob/master/holms-hound-of-the-baskervilles.epub
https://github.com/toshiakikoike/epub_file/tree/master/holms-hound-of-the-baskervilles

Product

  • Other
    cloud-reader from readium-js-viewer(develop), in the dist folder contents (generated by npm run dist):
    hypothes.is plugin active
    2.28.0-alpha

Chrome extension(from Chrome Web Store) has no problem.

Additional information

For example, "book_0003.xhtml" has 3 fragment identifiers;
<h3 class="mystyle_heading-2" id="toc-002">Chapter 1</h3> -- this fragment is in the top of this html file.
<h3 class="mystyle_heading-2" id="toc-003">Chapter 2</h3> -- this fragment is in the middle of this html file.
<h3 class="mystyle_heading-2" id="toc-004">Chapter 3</h3> -- this fragment is in the middle of this html file.

In toc.xhtm;
<li><a href="text/book_0003.xhtml#toc-002">Chapter 1</a></li>
<li><a href="text/book_0003.xhtml#toc-003">Chapter 2</a></li>
<li><a href="text/book_0003.xhtml#toc-004">Chapter 3</a></li>

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions