Created attachment 48247 [details] Sample files demonstrate the bug Add a new color to LibO (Options / Colors) With these components : R : 53 G : 133 B : 218 Write some text and set this color os text color and background color. We can read the text so, the color rendered is not the same. The expected behavior is that the color of the text must be the same as the background. From my tests, it is the background color that is not good.
Not reproduced with LO 3.4.1 (OOO340m1 (Build:101)) Ubuntu 10.04.2 x86 Linux 2.6.32-32-generic Russian UI
Created attachment 48328 [details] Screenshot of the bug
The bug occure with LibreOffice 3.4.1 OOO340m1 (Build:101) MacOS X Leopard (10.5) Intel Core 2 Duo I've join a screenshot of the bug where you can distinguish the differences on rendered colors.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
This bug always occur with LibreOffice 3.5.5.3 Version ID : 7122e39-92ed229-498d286-15e43b4-d70da21 On MacOS 10.7 Lion
Created attachment 64672 [details] Screenshot showing text on background with the same color, still readable (LibO 3.5.5.3 on MacOS X 10.6.8) REPRODUCIBLE on MacOS X 10.6.8 (Intel) with * LibreOffice 3.5.5.3 (Build ID: 7122e39-92ed229-498d286-15e43b4-d70da21) * LibreOffice 3.6.0.2 (Build ID: 815c576) both with German langpack installed. I created a color according to the original reporter's suggestion (R=53, G=133, B=218), applied it both text color and text background color and/or paragraph background color, and can confirm that the text is still readable, i.e. that the text color gets rendered differently from the background color. See the attached screenshot.
Analysis of my screenshot (attachment 64672 [details]) shows that the text color is rendered correctly (R=53, G=133, B=218), but the background color is rendered rather differently: (R=63, G=155, B=219).
Created attachment 64747 [details] Screenshot showing the same document, but in LibO 3.5.5.3 on WinXP: no color difference And now I understand why nobody else complains about this issue: it is NOT reproducible with LibO 3.5.5.3 on Windows XP Professional. To test, I used the same file as on MacOS X (screenshot: attachment 64672 [details]), but the result is different: on WinXP, the text is no longer visible (only the wavy red line shows where it is). Therefore, on Windows the display of text color and background color is correct (matching), only on MacOS X the background color is rendered incorrectly. Could someone else please test on some Linux variant, please?
REPRODUCIBLE with the same results also with Calc and Impress (LibreOffice 3.6.0.4 [Build ID: 932b512] on MacOS X 10.6.8 [Intel]): If I use the color defined as (R=53, G=133, B=218) both as text color and as cell/page background color, the color is rendered correctly for the text, but again wrong for the background -- both the cell background color (Calc) and the page background color (Impress) is rendered as (R=63, G=155, B=219). Therefore not only a Writer bug -- changed Component field accordingly.
@Thorsten Behrens: This is yet another MacOS-specific bug, therefore I add you to the CC list, sorry ;-) Please take a look at it. Thank you very much in advance! Rationale: Why does this bug deserve special attention? This issue seems minor at a first glance (no crash, no data loss, etc.), but is nevertheless blameful for LibreOffice: a user could ask us, “Can’t you even render a color correctly? When you can render it correctly in the text, why don’t you render it correctly for the background?” Additionally, bugs like this one make it difficult or even impossible to transfer Corporate Identity specifications (which often require careful color handling) to LibreOffice documents, and also reduce LibO’s value for publishing use. I could not find out if we have a developer especially experienced in color handling/rendering issues; if there is one, please contact him, as he could probably take this problem. Thank you again!
Still happens with Version 3.6.3.2 (Build ID: 58f22d5) On Mac OS X Lion 10.7.5
Any update with more recent LO versions like 4.1.5 or 4.2.2?
Bug still present in version 4.2.0.4 on Mac OS 10.9.2 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO
Bug still present in version 4.2.6.2 on Mac OS 10.9.5 Build ID: 185f2ce4dcc34af9bd97dec29e6d42c39557298f
Hm it looks like this bug was confirmed in the past so moving to NEW as REOPENED is incorrect.
** 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.4 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 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-12-20
Bug is still present Interestingly the text only shows after you start scrolling in the document. At open and when moving in the document with the cursors the text stays hidden, but as soon as you scroll the text appears in a different shade Also present in Libreoffice 3.3 at open LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Version: 5.3.0.0.alpha1+ Build ID: 17e9dc436bc6ad8d3a5bbde15d4d47262650aa2c CPU Threads: 2; OS Version: Mac OS X 10.12; UI Render: default; Layout Engine: new; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2016-11-06_01:25:01 Locale: en-US (en_NO.UTF-8); Calc: group
** 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
Still present Version: 6.0.0.0.alpha1+ Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-25_23:45:02 Locale: en-US (en_US.UTF-8); Calc: group
Dear fabien.michel, 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
Can't reproduce with Libreoffice 6.3.0.4 on Manjaro Linux. (=>text has exactly the same color as background)
Thank you for your feedback. Let's put this old one to WFM then since there's no specific commit about this.
This is a Mac bug, so reopening
(In reply to eisa01 from comment #25) > This is a Mac bug, so reopening you’re right, i was just focused to the fact the last comment was from the initial reporter.
This is still present It appears and disappear by selecting and scrolling a bit :) Version: 6.4.0.0.alpha0+ Build ID: 1c539c548b662104431e283aa4a62cb81174380b CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-08-28_05:21:39 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear fabien.michel, 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://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
I can no longer repro this Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 9bfc42015acd6ae3475ab7927ccc006507cc38a2 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded