[Libreoffice-ux-advise] [Bug 150067] improve Writer status bar

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=150067

Rafael Lima <rafael.palma.lima at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise at lists
                   |                            |.freedesktop.org,
                   |                            |rafael.palma.lima at gmail.com
           Keywords|                            |needsUXEval

--- Comment #1 from Rafael Lima <rafael.palma.lima at gmail.com> ---
The Insert / Overwrite section of the status bar does disappear when the window
width is reduced to around 40% of the screen size (in a 1920x1080p display).
The problem is that it disappears before other seemingly less important
sections as the Page Style and the Word Count. Maybe it should have higher
priority and remain visible, thus hiding Page Style and Word Count before
hiding the Ins/Ovr.

I also agree that the "Insert" status should be visible (explicitly written to
the status bar) as is the case with the "Overwrite" status. I don't know why
the "Insert" status is hidden and the "Overwrite" status is explicitly written
to the status bar. Both should be explicit.

BTW this is the expected behavior documented in the Writer Guide: "Insert mode:
This area is blank when in Insert mode. Click to change to Overwrite mode;
click again to return to Insert mode."

IMO we could do the following:
1) Make it explicit that we are in "Insert" mode in the status bar
2) Make it so this section disappears after the Page Style and Word Count
sections.

I wouldn't move the Ins/Ovr section to a different position in the status bar
(as suggested by the OP) because most users are used to its current position
and changing it would annoy many users.

Let's hear from the UX team.

-- 
You are receiving this mail because:
You are on the CC list for the bug.