Created attachment 50912 [details] Textbox with wrong background colour for edited text When editing text on an object (e.g. textbox or rectangle) the background (bg) of the edited text will change to the bg colour of the page instead of that of the object. This is handled OK for white or black page bg as the bg of the text will change to white or black depending on the colour of the text itself to give good contrast. But when page bg is different from pure white or black then the bg of text edited e.g. in a textbox will be that of the page bg. Instructions: 1) Create new Writer document and change page bg to e.g. "Gray 10%" 2) Create textbox with dummy text and change textbox bg to "Black" 3) Mark text in textbox and change text colour to white 4) Edit text in textbox e.g. by adding more characters => bg of edited text will change to "Gray 10%"! This renders editing text in textboxes or other objects impossible in many situations. Things get worse when an image file is used as bg for a page, as Writer will use bg colour "Black" in this case. Instructions: 1) Create new Writer document and change page bg to "Graphic" (any image file will do) 2) Create textbox and start writing => bg of edited text will change to "Black" and makes text invisible since "Black" is default colour for text!
tested these exact steps on 3.4.3 English install, Windows XP sp3 (32 bit) JRE 6u26. The background of the new text (step 4 of instructions) did change to the 10% grey while I was typing, but once I clicked out of the text box, the background changed back to black. Same with all shapes - background does change to the page bg while editing, but changes back to the shape/text box bg when I click out of it.
I think I misunderstood your bug report - you weren't saying the bg stayed that way, just that it was hard to edit because the colors changed. I confirm that the colors are as you described and that it does make it hard to create text boxes or edits if the bg color is similar to the text color.
(In reply to comment #2) > ... you weren't saying the bg stayed that > way, just that it was hard to edit because the colors changed ... Yes exactly! Sorry if my bug report wasn't overly clear on that.
I can confirm that... Win7 64 bit LibO 3.4.3 Build:302
I can confirm this behavior for LibO 3.4.4 Linux Ubuntu 11.10 64-Bit an for LibO3.5.0rc1 in WindowsXP! While editing text in those text-boxes it could be unreadable during edit text in it, because the background-colour changes to the backgroundcolour of the page instead of the text-box!
Created attachment 56508 [details] test case
reproduced in LibO 3.6.0 master and in 3.3.4 on Fedora 64 bit change version to 3.3.4 (most early reproducible)
Effect is reproducible with "LibreOffice 3.5.3.2 (RC2) German UI/Locale [Build-ID: 235ab8a-3802056-4a8fed3-2d66ea8-e241b80] on German WIN7 Home Premium (64bit), but I don't know whether it's a bug? Behaved the same way with LibO 3.3.3 and OOo 3.3, inherited from OOo. The only really bad thing I see is the black paragraph highlighting if page has bitmap background, but I am not sure whether that really has the same roots. @all: Everything else did not cause real problems, why do you think that that is a bug?
Created attachment 60796 [details] Screenshots I can not see a real bug
I really wonder for what that highlighting 8it's not exactly paragraph-, more row-highlighting is required in the text box
Your example actually _has_ some contrast. White text on "Gray 10%" is very difficult to read and I could imagine that even your example is difficult on cheaper screens with TN-panel (I am sitting in front of an IPS-panel and cannot tell). I know the case of "white on gray 10%" sounds like an artificial construct that would never occur in real life, but I filed this bug report because it actually happened to me. (I probably used other colours but I don't remember which ones) Is it so difficult to make LibreOffice show the object's colour as background colour instead of the page colour?
** 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 (4.4.1 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-04-01
Still reproduced. You have to write something to see the change. Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64) Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9 TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50 Locale: fi_FI
Bug still present without changes in LO v5.0.4.2 on Windows Server 2012 R2 (Windows 8.1)
** 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.2.5 or 5.3.0 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-20170306
Seems to work fine in in 5.3.0.3 (x64) on Windows 10 Pro :-)
Seems to work fine in 5.3.0.3 (x64) on Windows 10 Pro :-)