Created attachment 58553 [details] Screenshot See the screenshot. Here KWord is on the left, MS Word 2003 on the right and LO Writer in the center. See how text sheet background blends with toolbars in color in Writer making it look really modest compared to the other two apps. I think there should be some contract between the edit space and toolbars.
Hmm, it appears that this bug is only applicable to GTK version of LibreOffice theming. When libreoffice-kde is in use or when starting Windows version via Wine, this bug doesn't appear.
Is this still happen on latest stable release?
Yes, still there [1]. [1]: http://i0.simplest-image-hosting.net/picture/screenshot-06282013-115927-am.png
for me not reproducible with LO 4.3.2.2 (Win 8.1) Does this issue still persist for you or anybody else with the latest release of LO? Otherwise, we could maybe close this issue.
Created attachment 106948 [details] Screenshot as of 4.3 Yes, I still reproduce this on Linux. In fact, it's become even worse since the frame has been removed.
Thanks for your very fast reply. On Windows I don't have this problem. Then it is maybe a Linux only issue? Do you also have the possibility to test it on Windows (maybe at a friend)?
Created attachment 106956 [details] Screenshot on Windows Works OK in Windows now, although it didn't as of 4.0. So may be a Linux-only problem now. Don't know what about MacOS X.
Thanks for confirming that it is ok on Windows. Let's mark it as Linux as long as nobody confirms this bug also on Mac OSX.
** 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 on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Migrating Whiteboard tags to Keywords: (needsDevEval)
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Created attachment 130124 [details] Screenshot as of 5.3 Still present in LibreOfficeDev 5.3.0.0.beta2.
This bug was incorrectly moved from NEEDINFO to NEW by the reporter. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
(In reply to Xisco Faulí from comment #13) > This bug was incorrectly moved from NEEDINFO to NEW by the reporter. What do you mean by "incorrectly"? Have you seen comment #12?
A bug can go from NEEDINFO to NEW. it need to go to UNCONFIRMED until someone else confirms it.
Still the same problem in 5.3.3.
Since the menu can be customized using Firefox personas, I don't consider this a bug. An example of how to use personas: https://www.youtube.com/watch?v=ccFUl7RlgjE&hd=1 Closing as RESOLVED NOTABUG
(In reply to Xisco Faulí from comment #17) > Since the menu can be customized using Firefox personas, I don't consider > this a bug. An example of how to use personas: > https://www.youtube.com/watch?v=ccFUl7RlgjE&hd=1 > Closing as RESOLVED NOTABUG Customization of toolbars doesn't customize document background. I'd rather consider the personas as a crutch, necessary to get rid of bad defaults.