I propose adding Alt+left/right shortcut to Navigation back/forward functionality on default. The Alt+left/right shortcut for moving back/forward has been adopted in all web browsers and even Adobe Acrobat for a while now. I think it would also make sense to enable these shortcuts in LO also. Currently the back/forward navigation feature is in my opinion a little unknown for a lot of people, because it is not included in the default toolbar setup. User has to know it exists and enable it from View->Toolbars->Navigation. If this functionality would be mapped to well known shortcut, maybe people could find it easier. If possible, I would also advocate for mapping the back/forward navigation functionality to the related mouse buttons too.
The Navigator sfx2 Recency stack--controlled either by the Navigation Toolbar buttons 'Back'/'Forward' or the Sidebar Navigator when placed in 'Recency' "navigate-by" mode functions without issue, as refactored for see also bug 115817 or bug 51401 Though correct that no shortcut is assigned to the associated UNO: .uno:NavigateBack or .uno:NavigateForward And while the <Alt>+<Left> or <Alt>+<Right> are available for user to customize, do not believe there is a strong requirement to make such shortcut assignment. "Eve" users sufficiently motivated to use the movements via keyboard can customize to do so. "Benjamin" users are well served by either the 'Navigation' toolbar, or the Navigator placed into 'Recency' mode. IMHO => WF
I got to test Word 2013/2019 and both have default mapping of Alt+left/right shortcuts to back/forward navigation functionality. IMO this would support adding the same shortcut mappings also to Writer as default. Word 2013/2019 do not have back/forward mapping of the corresponding mouse keys, However, newer versions might have this, but I don't have access to newer versions to test.
@Stuart, now knowing that MS Word has had these shorcuts enabled at least since 2013, do you still consider that there is not a strong enough requirement to enable them in LO Writer by default?
My position/input to UX remains as in comment 1 Its an easy hack if that is UX consensus.