https://bugs.documentfoundation.org/show_bug.cgi?id=171212
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #13 from V Stuart Foote <[email protected]> --- The UNO for the by page navigation exist and respond to assigned keyboard shortcuts-that can be customized by user to preferences. Similar function is also implemented in the UI on the Navigator SB deck(s) in the 'Navigate by page' mode. Slight difference in UI for view port of results between keyboard or the Navigator movements. The UNO based movements (.uno:GoToStartOfNextPage, .uno:GoToStartOfPrevPage) calculate a view port that shows the page break and part of the adjacent page. The Navigator "by Page" mode positions with view port to fully expose the page. Also, the UNO based movements by shortcut position the edit cursor into the revised view port, while the Navigator movement does not (and requires an edit cursor focus action). Open to discussion if the two methods to position "by page" should match exactly, but issue of OP is not valid. Feature "shortcuts to go to previous and next pages" already exists. -- You are receiving this mail because: You are the assignee for the bug.
