https://bugs.documentfoundation.org/show_bug.cgi?id=172951
Heiko Tietze <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Blocks|86899 |108075 Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org |tion.org Ever confirmed|0 |1 Summary|Better support of two-page |Make PgDown/Up scroll to |working (face2face, book |the next row if visible |view): Pgup/dn for two-page | |thumb through | --- Comment #10 from Heiko Tietze <[email protected]> --- We discussed the topic at the design meeting. Bending .uno:GotoNextPage into something like .uno:GotoNextPagesRow sounds wrong and is surely breaking the use case for people who trust in "next page". In particular the modification is wrong at the GoTo dialog and the Navigator, where clicking up aka Next Page iterates to the next row ening up in some other value but +1. We double checked how MSO handles the topic and PgDown behaves differently depending on the zoom level. It either goes to the usual position if the end of the page is not shown or to the beginning of the next page otherwise; in multi-page mode the same happens and PgDown stays either on the same page or continues to the next row. The action "Next Page" always continues to the next row of pages, but it has no UI and is therefore actually GotoNextPagesRow. We agreed to pimp the PgDown behavior so that it either scrolls down the amount specified in the OS/DE or if the next page is visible jumps to the beginning of the next page *below*, ie. the next row. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86899 [Bug 86899] [META] Requests for the addition of UNO commands https://bugs.documentfoundation.org/show_bug.cgi?id=108075 [Bug 108075] [META] Scrolling and Page up/down issues -- You are receiving this mail because: You are the assignee for the bug.
