Description: The 'typing cursor' and 'I bar' (what the mouse pointer changes into when you move it over the document) are very faint and hard to see if you set your background to anything other than white. This is especially annoying when you set the Libre Writer to dark mode and have the background colour a shade of grey. The reason I do this is because my main display is an OLED monitor and it's a bad idea to have an OLED sit on white for hours on end as this will lead to my monitor having pretty severe burn in over time. All the solutions I have seen for this problem always tells people to just alter the cursor settings in Windows settings. However for some reason this does not work for libre writer, I change the cursor width and set up coloured indicators on the cursor, but they do not show up or do anything for the cursor in Libre Writer. Actual Results: Go to 'tools' then 'options' then 'application colours' and change 'document background' to colour '#7B7B7B'. Expected Results: Changed document background colour to a darkish grey, then you should notice the 'typing cursor' and 'I bar' are quite faint and hard to see. Reproducible: Always User Profile Reset: No Additional Info: Allow me to change the colour and size of both the 'typing cursor' and 'I bar'. I'm using Windows 11 Pro.
I confirm it with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 069c7dc4e9706b40ca12d83d83f90f41cec948f8 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Tools -> Options -> LibreOffice -> Application Colours 2. Change colour of dicument background to #7B7B7B 3. Write some wrds and plac cursor behind a word and move with mouse or touchpad over document Actual result Cursor almost unvisible Expected result Cursor should be visible So for me it's a valid enhancemnet request, but I add design-team to find a solution here.
The text cursor does toggle color in response Application Colors 'Document background' set. Easier to see the effect if the document background is selected across the range of the Standard palette's gray scale. It is not the size or shape of the text cursor (and do not think we need to follow any os/DE settings cross platform). Rather, issue is that the transition of text cursor's gray scale color against background color does not auto-adjust well and you *can* end up with "invisible" Grey cursor on Grey 'Document background' and similar low contrast values around the gray-scale mid-range. Suggests there should be a test of text cursor contrast against document background for auto-adjust. Also in addition to contrast testing for automatic values, I would love to be able to directly set the text cursor and pointer color as Application color elements.
Not adjusting the cursor color depending on the background is a bug. I wonder if Hossein's latest patch does something good here too. See bug 122970 (and bug 155943 as follow-up to-do).
(In reply to V Stuart Foote from comment #2) > The text cursor does toggle color in response Application Colors 'Document > background' set. Does it? Same greyish color on black document background as on white.
Created attachment 188108 [details] Text cursor light - dark cross over at 50% grey. Win10 in os/DE dark mode. (In reply to Heiko Tietze from comment #4) > (In reply to V Stuart Foote from comment #2) > > The text cursor does toggle color in response Application Colors 'Document > > background' set. > Does it? Same greyish color on black document background as on white. Yes. See the attached--the cross over happens at the 50% grey. And where the cursor disappears into the canvas. There is no contrast testing of cursor fg against canvas bg.
Obviously a bug probably caused by XOR rendering (see bug 122970) that fails at this particular value.
(In reply to Heiko Tietze from comment #3) > Not adjusting the cursor color depending on the background is a bug. I > wonder if Hossein's latest patch does something good here too. See bug > 122970 (and bug 155943 as follow-up to-do). The above bug (tdf#122970) is related. The way LibreOffice renders the typing cursor using XOR is problematic, and should be changed in a similar way. But the fix (or a separate patch) should also take care of the specific colors used for the typing cursor. (In reply to Heiko Tietze from comment #6) > Obviously a bug probably caused by XOR rendering (see bug 122970) that fails > at this particular value. Yes, this is a bug. I think using the typing cursor provided by the OS/graphical back-end is the way to go. There are customization like the arrow that shows the direction of the writing inside text with different direction. They might be implemented similar to the way suggested in tdf#155943 through OS/back-end provided means. Might not be straightforward. These are not visible with Skia right now anyway.
Dear Davn_n1, 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