See attached screenshots. The buttons in the document properties windows change position when clicked. Ie. click in the top row and the top and bottom rows swap.
This violates a fundamental principle of UI and impedes muscle memory. The selected button should change appearance (which it does) to indicate that it's selected but it should not move.
Steps to Reproduce:
1. Open a document
2. File > Properties...
3. Click any button in the top row
rows shouldn't swap.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Created attachment 136031 [details]
Created attachment 136032 [details]
I guess they move because of wanting to keep the active tab immediately next to the content area.. It is a bit confusing. Let's ping UX.
And what happens if you drag the Properties dialog wider?
The stacking of the tabs makes it seem as if they shift--they don't. NAB
Well, this tab-shifting behaviour is in all dialogs with enough tabs, like formatting etc.
Seems to be a NOTABUG because it's worse usability to have tabs that are hanging "in the air" and not linked to the tab content. Is tab appearance not part of the OS design and not changeable by LibO?
At least in Windows and Linux operating systems, when a dialog contains more tabs than its width allows, the active tab will always be displayed next to its container, and its row will shift to be below, or closest to you, of you can picture a literal stack of folder tabs. That is the metaphor, and it’s an expected behavior. During the ’90s, it used to be common for a tab strip to overflow by remaining in a single row but sliding (as Firefox does today), but this was abandoned because it hid the options from the user, hurting discoverability (not an issue for Firefox, where the tabs are actually the content the user explicitly opened).
This makes it a WONTFIX… Except that in 6.0, this dialog was made a little wider so that it can accomodate the tabs in a single row, so you won’t see two rows anymore.
*** Bug 118384 has been marked as a duplicate of this bug. ***
*** Bug 105243 has been marked as a duplicate of this bug. ***
*** Bug 118272 has been marked as a duplicate of this bug. ***