<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - "Previous page" and "Next page" functions in navigator not available for keyboard binding" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101211#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - "Previous page" and "Next page" functions in navigator not available for keyboard binding" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101211">bug 101211</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to Commit Notification from <a href="show_bug.cgi?id=101211#c36">comment #36</a>) > Jim Raykowski committed a patch related to this issue. > It has been pushed to "master": @Jim, I'll have to test when it rolls, but is cursor focus moving with the page repositioning? Or, are we now just scrolling in full page increments? Unclear from the comments in <a href="https://gerrit.libreoffice.org/c/core/+/91605">https://gerrit.libreoffice.org/c/core/+/91605</a> While the current pgDn/pgUp .uno commands scroll (leaving cursor focus behind); seems like doing so with full page movements is going to cause some annoyance at needing to mouse click into the page view to gain cursor focus. Also, what keyboard shortcut assignment adjustments to be made--the <Ctrl>+pgDn/<Ctrl>+pgUp used by toFooter/toHeader need to be moved to free them up for full page movements.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>