Description: If you use combined characters like u0326 and then a background color on the following character, the right-most parts of the combined characters are not visible. Steps to Reproduce: 1. type a digit like 2 2. type SHIFT-CTRL-u 0 3 2 6 ENTER to get "non space consuming" comma 3. type another digit like 7 and mark it 4. choose a background color for the 7 Actual Results: The comma is hidden behind the background color Expected Results: The combined character should either be on top of the background color or not being affected of the background color of the following character. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.4.2 Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.utf8); UI: de-DE Calc: threaded Turning off the hardware acceleration does not change the behavior.
I can't confirm it with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f96004096268f5e71120678e32fc8c74055819aa CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL But perhaps I misunderstand something. Could you please add a screenshot that shows the problem or perhaps a sample document including steps 1 to 3? Thank you. => NEEDINFO
Created attachment 170893 [details] screenshot Screenshot of the problem. First line is 2,7 with the u0326-comma without background. In the second line the 7 has a background-color.
Created attachment 170894 [details] test-document Document from which the screenshot was made
I added some attachments that hopefully help. This behavior does not change when the 2 also gets an explicit background.
Hello libreoffice@bnm.me, Thank you for reporting this bug. I can reproduce this bug. Version: 7.0.4.2 Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded I am changing the status of this bug to NEW.
bug is still valid in 7.3.3.2
*** This bug has been marked as a duplicate of bug 43643 ***