forked from crosspoint-reader/crosspoint-reader
-
-
Notifications
You must be signed in to change notification settings - Fork 58
fix(koreader): resolve element XPath progress against visible body text #261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
uxjulia
merged 3 commits into
uxjulia:development
from
crosspoint-reader:fix/koreader-xpath-parsing-#2307
Jun 13, 2026
+184
−47
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a
scriptorstyleblock contains a literal<(for exampleif (a < b)), this ignore branch is never reached because<is handled earlier as a tag opener. The later real</script>/</style>can then be swallowed as attributes of that bogus tag, leavingnonVisibleDepthnonzero and causing all following body text to be skipped, so KOReader progress mapping falls back or resolves near the start for EPUBs with inline scripts/styles. While inside these non-visible raw-text elements, bytes need to be ignored until the actual closing tag rather than fed through the normal tag parser.Useful? React with 👍 / 👎.