Description: When editing chart data series (also present in Data Table) there are numerous graphical artifacts visible inside window. AT first it looks like minor issue, but these overlaps can make navigating harder. Steps to Reproduce: 1.Create chart 2.Double click it (or open any kind of properties window) Actual Results: Graphical artifacts present in window Expected Results: No graphical artifacts present in window Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Mac OS X 11.7.3; UI render: Skia/Raster; VCL: osx Locale: en-US (en_UA.UTF-8); UI: en-US Calc: threaded
Did not find a way to attach screen, so here is a link to my drive: https://drive.google.com/file/d/1K3m1hn9_9QOVLllIF7oReoXcuVoH2xPC/view?usp=share_link I will keep this link working until issue is resolved/acknowledged. Thank you for LibreOffice!
Created attachment 185389 [details] screenshot of issue Here it is attached to the report, you can turn that share off now if you want.
Could not reproduce in: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 2; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I tried by right-clicking on the chart area and selecting "Format chart area", then switching tabs. I also tested with Skia/Raster rendering, no issue. Can you please provide more precise steps, like how you switch tabs, to observe the issue? Does it happen with any dialog that has tabs? Are you sure it does not happen in other apps? Thank you!
Sorry for late reply. On my machine this issue is always reproducible but at this moment I have no ability to test it on other machines. I did upgrade from previous version so did not clear profile configuration (which may be the case). Also I have additional configuration that may shed light on this problem. Attached two screens via link (bug is present in settings too as you can see). Hopefully this is not global and affects me only, but I can not say for sure. Screen #1 (configuration): https://drive.google.com/file/d/1KEo_oXjIv8PbSPFI9kCFPz03V-gmae7z/view?usp=share_link Screen #2 (configuration): https://drive.google.com/file/d/1KJW_fyM07n85WaPoltecR4W0O8cCodcp/view?usp=share_link May be related to hardware acceleration.
[Automated Action] NeedInfo-To-Unconfirmed
This sounds like the same issue as bug 152220 that I could not replicate Do you see the same issue in that bug on latest 7.5? Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
(In reply to eisa01 from comment #6) > This sounds like the same issue as bug 152220 that I could not replicate > > Do you see the same issue in that bug on latest 7.5? > > Version: 7.5.1.2 (AARCH64) / LibreOffice Community > Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 > CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded > > Version: 7.5.1.2 (AARCH64) / LibreOffice Community > Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 > CPU threads: 10; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded Yes, so far bug is always reproducible on my side, even with latest LibreOffice version. Screenshot: https://drive.google.com/file/d/1KoFpO3RAefAtICAU4dcAEV2uQgpHNcXC/view?usp=share_link
Sounds like the same issue as 152220, as Eisa pointed out. Which allows us to set that one to "New". Vadym, would be great if you could confirm there that it only happens in macOS dark mode (or not). Thank you both! *** This bug has been marked as a duplicate of bug 152220 ***