https://bugs.documentfoundation.org/show_bug.cgi?id=171259
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Adjust view port of UNO "To |Change default full page |Begin of Next/Prev Page" to |movements |match Navigator "by Page" |(<Alt><PgDn|PgUp>), for a |and "Go to Page..." |top aligned viewport from |movements |GoToNextPage/GoToPrevPage, | |to match Navigator "by | |Page" movements --- Comment #3 from V Stuart Foote <[email protected]> --- (In reply to V Stuart Foote from comment #2) > Sorry, just poorly worded. > > Yes, the Navigator "by Page" instance matches the "Go to Page..." dialog > instance. And movments position view port to full pages with breaks at the > top edge. > > What would be of use would be if the page movements associated with the > .uno:GoToStartOfNextPage / .uno:GoToStartOfPrevPage could receive the same > view port as the Navigator "by Page", or the "Go to Page..." widgets. The > breaks at the top edge rather than showing part of the previous page and the > target page. @Jim, you are exactly correct as usual--the "Go to Page..." dialog splits he viewport between the pages. It matches the viewport result for the Go to Start of Next/Prev Page UNOs. And those are what are now applied to the <Alt><PgDn> / <Alt><PgUp> shortcuts Currently only the Navigator "by Page" gives the movement viewport we'd be looking for. Which is the alignment of the viewport to the top of the target page. /me mistaken in the UNO idents -- .uno:GoToNextPage and .uno:GoToPrevPage match what the Navigator deck "by Page" mode gives. They are not currently assigned a shortcut, while changing the UNO assignments to use them instead does exactly what is asked. Only question for UX advise now is if we should swap out the UNOs assigned the default shortcuts? Use the Go To Next/Prev Page and its top alligned viewport by rather than the split view port? -- You are receiving this mail because: You are the assignee for the bug.
