Issue Page and Displayed page mismatched if Front Matter included
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Here is an example screenshot:
Notice the "Next Issue" button lacks a matching "Previous Issue" button.
Granted the only logical way to work through the document is from front to back, but if one is cruising through the document to see what impact a change might have on following pages, it would be sensible to be able to jump back to the page with an issue.
(The other "issue" in the screenshot is the fact the printed page numbers don't match the PDF's numbers nor the Check pages list. The page numbers don't match, because the "front matter" throws the PDF pages off the printed pages. This is normal for people who are used to messing about with PDFs, but this would be startling to most field teams --Not sure what the solution might be so that this isn't confusing to field users.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named; begin by reproducing the screenshot scenario with a document containing front matter and inspect how the issue page, Next Issue, and Previous Issue navigation are determined. Done should include consistent navigation and a clearly resolved or documented relationship between printed page numbers, PDF pages, and the Check pages list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100