Opened 8 years ago
Last modified 6 years ago
#315 new defect
Navigation pane is not kept in sync with location in document when contents are nested
| Reported by: | Lewis Rosenthal | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.4.1 |
| Component: | UI | Version: | 1.3.6 |
| Keywords: | Cc: |
Description
When the Navigation pane has nested contents, moving from page to page non-sequentially via the toolbar or the Go to page dialog will not reposition (or expand) the tree.
It seems that the first two digits entered the first time anything is entered will move the bounce bar in the nav pane. After that, First/Last, Previous/Next, or any entry in the field generally leaves the bounce bar in place (thus, it moves once).
I was able to get it to finally expand a section with a page jump from the Go to page dialog, but only once in a 125-page document.
Attachments (2)
Change History (5)
by , 8 years ago
| Attachment: | Nav_pane_in_sync.png added |
|---|
by , 8 years ago
| Attachment: | Nav_pane_out_of_sync.png added |
|---|
Jump to a page by entering the page number in the toolbar dialog. The Nav pane does not move to match the location in the document.
comment:2 by , 6 years ago
This is still an issue in 1.4.1. RC1. Quick, easy example is the DFSee HOWTO PDF. I managed to get the navigation pane to go to the bottom (End key), but Home left it there while properly displaying the correct page in the document.
comment:3 by , 6 years ago
Note that this ticket deals solely with the selection highlight in the navigation pane not being kept in sync with the document pane, whereas #265 deals with the page number indicator in the toolbar not being kept in sync with the document window content.
Initial document opening. Nav pane is in sync with the first page.