| Summary: | Ruler’s numbers and tick marks have low contrast when using dark KDE themes | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | gnomek <sabayon11> |
| Component: | UI | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | CC: | 4mr.minj, ilmari.lauhakangas, jmadero.dev, philipz85, sabayon11 |
| Priority: | medium | Keywords: | needsDevEval, topicUI |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=90214 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 102495, 103184, 108629 | ||
| Attachments: | LibreOffice 5.4 running on KDE 4.14.2 with a dark theme, emphasis on the visible ruler elements | ||
|
Description
gnomek
2014-11-23 10:50:51 UTC
> Is there any way user can do something about it?
Tools > Options > Appearance > Application background, change the color to suit your preference, and then restart the application.
No. This is not the right solution. http://i.imgur.com/14hahY0.png Sorry. This one is after Writer restart. No desired effect. http://i.imgur.com/XrCNvpX.png (Clarifying the issue’s title) Not limited to KDE - also a regression. See also bug added. Why is this marked as an EasyHack? EasyHacks require developer input and code pointers. I don't see that at all here. Setting to needsDevEval (proposed easy hack) to try to get a code pointer. Isn't this a bug since color seems to be set to <clBlack> instead of system setting <clActiveWindowText> (or however it is called here). Changing severity/priority: Severity: minor - can slow down professional quality work but will not prevent it; Importance: low - default for minor issues. The workaround is obviously to just not use a dark theme (I know not perfect...I like dark themes also) The see also bug has a bibisect to at least identify where the partial regression came from (before the color of the numbers were white when using a dark theme). But from what I can tell the color of the tab stops have always been dark which I agree - makes the ruler very hard to use with a dark theme. I still suspect that this is an easy hack so I'm going to leave needsDevEval to try to get a code pointer and maybe someone will become interested enough to look into it. Thanks all! Migrating Whiteboard tags to Keywords: (needsDevEval, topicUI) [NinjaEdit] > I still suspect that this is an easy hack
Can you please tell me if I can hack it myself by editing any file and how to do it?
I know you have priorities but this problem forces me to use bright themes that make my eyesight worse.
Would be good to test if this is fixed in KDE after bug 90214 has now been fixed. Created attachment 130197 [details]
LibreOffice 5.4 running on KDE 4.14.2 with a dark theme, emphasis on the visible ruler elements
Checked this with 5.4.0.0.alpha0+ on KDE 4.14.2 and the ruler markers are visible on a dark theme (check the screenshot).
I can confirm it works in http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/2017-02-15_23.38.34/ But can you push it to 5.3.1 please? Please don't let all users wait a few months for 5.4 official release. It is important for for dark theme users. Anyway, thank you very much for this fix. ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug It looks ok now: https://imgur.com/a/btmIbqe Version: 6.0.5.2 Build ID: 1:6.0.5~rc2-0ubuntu0.16.04.1~lo1 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: kde4; (In reply to gnomek from comment #15) > It looks ok now: > https://imgur.com/a/btmIbqe > > Version: 6.0.5.2 > Build ID: 1:6.0.5~rc2-0ubuntu0.16.04.1~lo1 > CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: kde4; Then let's close. *** This bug has been marked as a duplicate of bug 90214 *** |
