Bug 146789 - Inaccurate documentation of Writer Keyboard shortcuts
Summary: Inaccurate documentation of Writer Keyboard shortcuts
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
7.2.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Mac
  Show dependency treegraph
 
Reported: 2022-01-15 23:14 UTC by MarjaE
Modified: 2024-03-12 05:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MarjaE 2022-01-15 23:14:35 UTC
The Getting Started guide 7.1 states that Home and End move to the beginning and end of the current line. The Writer Guide 7.2 for MacOS doesn't say otherwise. In Writer on MacOS, they move to the beginning and end of the document. This is more intuitive, but the documentation hasn't caught up, and doesn't help users find their actual keyboard navigation options.

The Getting Started guide 7.1 states that Control-Home and Control-End move to the beginning and end of the document. In Writer in MacOS, they do nothing.

There is no consistent pattern between the described behavior of nav keys in the documentation, and their changes with Control and Command, and their actual behavior.

Part of this is probably because MacOS often uses Command+Up as a sub for Home and Command+Down as a sub for End.

I'm not seeing any options in System Preferences > Keyboard > Shortcuts which would affect this.

I'm not seeing any options in LibreOffice, but I have a very hard time reading those preferences because they're far too small.

Related: bug 32663.
Comment 1 Rafael Lima 2022-01-21 14:07:15 UTC
Hi Marja. I believe this issue persists in the Getting Started Guide 7.2 as well, on page 137 that states: "Home moves the cell focus to the start of a row."

I do not have a Mac to test the behavior of Home/End keys in MacOS.

I'll let the team in charge of GS Guide 7.3 know of your request.
Comment 2 BogdanB 2024-03-12 05:36:29 UTC
fpy@bger.ch, please argument your decision in changing the bug status. Until then don't touch bug status.