Description: The tabbed Notebook Bar has a host of display/usability issues on Windows 10: 1. Tabs are too small in height 2. Underlined Mnemonics add visual noise 3. Padding between text and border of tabs is too small 4. Not enough contrast between colors for currently active and inactive tabs 5. Buttons are poorly aligned, have no space between and are missing borders Overall, the Notebook Bar looks cramped and noisy. Lack of contrast makes it difficult to see, which tab is currently active. These layout problems impact usability. Tested on Windows 10 1809 with LO 6.2.5 Screen resolution: 4K (3840 x 2160) with 250% text scaling Steps to Reproduce: 1.View > User Interface > Tabbed Actual Results: cramped and noisy UI Expected Results: clean UI Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 152970 [details] Tabbed Notebar on Windows 10 HiDPI
Also in Spanish, in a HiDPI touchscreen, in OpenOffice 6.3.2.2 and every version of 6.2.x i have tested. The tab labels run together. This is not helped by the low contrast of the lines that separate the tabs.
Yes, it looks ugly without padding. What can we do, Sumit, Szymon?
(In reply to Damian Hofmann from comment #0) > 1. Tabs are too small in height > 2. Underlined Mnemonics add visual noise > 3. Padding between text and border of tabs is too small > 4. Not enough contrast between colors for currently active and inactive tabs > 5. Buttons are poorly aligned, have no space between and are missing borders In general ALL Notebookbars didn't use specific padding items, cause the reason is that I don't want to have .ui file specific settings. So if you can change the settings somewhere in the generic themes it will improve the NB but also ALL other ui elements. If I would add paddings to each element in the .ui file it may work better, but I prefer that this can be solved somewhere generic. 5. I would love if someone can tell me what I have to do that the select thing will fill height.
Sorry for the late reply, sometimes reports just slip through. Since some time has past by and the report consists of five different issues I'm going to resolve it as WFM with the hope some/many/all issues have been fixed meanwhile. If not, other reports are referenced with the meta ticket. Feel free to reopen, of course.
Created attachment 180510 [details] Squised Tabbed UI View
(In reply to Heiko Tietze from comment #5) > Sorry for the late reply, sometimes reports just slip through. Since some > time has past by and the report consists of five different issues I'm going > to resolve it as WFM with the hope some/many/all issues have been fixed > meanwhile. If not, other reports are referenced with the meta ticket. Feel > free to reopen, of course. Hey there, I currently still have all the listed issues on my 4k PC, I've attached a screenshot.
So let's keep it open as bug. We aim for a ticket per patch so the Continuos integration can be linked to the reported issue. Does not work wit multiple reports in one ticket. And the summary "usability issues" is nondescript too. It will be hard to find volunteers.
(In reply to Heiko Tietze from comment #8) > So let's keep it open as bug. We aim for a ticket per patch so the Continuos > integration can be linked to the reported issue. Does not work wit multiple > reports in one ticket. And the summary "usability issues" is nondescript > too. It will be hard to find volunteers. Sorry, this is my second day here and I'm not familiar with the process. Should I open my own separate bug or update the title for this one? Thanks for responding so fast!
(In reply to Ema S. from comment #9) > (In reply to Heiko Tietze from comment #8) > > So let's keep it open as bug. We aim for a ticket per patch so the Continuos > > integration can be linked to the reported issue. Does not work wit multiple > > reports in one ticket. And the summary "usability issues" is nondescript > > too. It will be hard to find volunteers. > > Sorry, this is my second day here and I'm not familiar with the process. > Should I open my own separate bug or update the title for this one? Thanks > for responding so fast! Your change to get something fixed is much higher in case of bite-sized and clearly framed issues. From quickly glancing over #0 I understand 1. and 3., 4. is somewhat difficult since we use the system theme, or should do so, 2. with "visual noise" and 5. with "poorly aligned" needs specification. It does not mean implementing a couple of patches for this broad topic is impossible. And some issues might have also been reported. I remember discussions on a11y, the tab size, and white space.
> 2. with "visual noise" The underlining of the MNEMONIC key makes the already cluttered UI even busier. It should normally be hidden and only shown, when the ALT key is pressed. > 5. with "poorly aligned" needs specification. What specification do you need? There's a clear example pointed out in the screenshot (see nr. 5), where the "Seitenleiste" button simply doesn't line up with it's neighboring buttons "Lineale" und "Gitter". This is one of many examples, where the buttons or groups have "strange" horizontal or vertical offsets to their neighbors for no apparent reason. > does not mean implementing a couple of patches for this broad topic is > impossible. And some issues might have also been reported. I remember > discussions on a11y, the tab size, and white space. Feel free to split into separate issues, if it helps fixing. But it's really not one individual thing for me. The poor use of margins, padding, bad alignments, etc. make the entire Tabbed Notebook Bar look unfinished and messy. It's the combination of all those things.
Dear Damian Hofmann, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Heiko Tietze committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/24aed2348395b234c6c35a504809ea6f5e97f5a1 Resolves tdf#126530 - Improve contrast between active and inactive tabs It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
This patch fixes the contrast issues with tabs making the active tab visually merge with the Notebookbar pane. It applies to all dialogs with tabs. The other issues should have been fixed meanwhile, resolving the ticket as fixed. (It was tagged as Windows but is also an issue for Qt. Follow-up patch incoming...)
Created attachment 203039 [details] Screenshot with kf5 and master as of 24aed2348395b234c6c35a504809ea6f5e97f5a1 for discussion in https://gerrit.libreoffice.org/c/core/+/191626
Created attachment 203040 [details] Screenshot with kf5 and https://gerrit.libreoffice.org/c/core/+/191626 for discussion in that Gerrit change
Spelling out the issues in the title (which is otherwise completely generic and vague). Also, nicely done Heiko, this really hits the spot! I hope that this fix didn't only happen just now because of our chat in the last design meeting... :-P