Bug 152849

Summary: conditional formatting entry field exists; but is not visible
Product: LibreOffice Reporter: Pierre Fortin <pf>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: m.weghorn, raal, rafael.palma.lima
Priority: medium    
Version: 7.6.0.0 alpha0+   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=147097
https://bugs.documentfoundation.org/show_bug.cgi?id=150451
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 102495    
Attachments: annotated screenshot

Description Pierre Fortin 2023-01-02 19:09:12 UTC
Same as bug 139246. Is this dependent on desktop?
The field exists; but without any visual indication, it leaves the user initially confused.
See https://bugs.documentfoundation.org/attachment.cgi?id=139246

Operating System: Mageia 9
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.1.1-server-2.mga9 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 125.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Dell Inc.
Product Name: XPS 8950
Comment 1 raal 2023-01-03 16:38:43 UTC
Please provide better description of the bug. Thank you
https://wiki.documentfoundation.org/QA/BugReport
Comment 2 Pierre Fortin 2023-01-08 22:04:37 UTC
Created attachment 184532 [details]
annotated screenshot

Hope this helps...
Comment 3 Rafael Lima 2023-01-09 19:06:37 UTC
I'd say this is a duplicate of bug 150451. Although it complains about dark mode, I believe it is the same root cause. Both bug reports are related to kf5.

Apparently the outline of text boxes is not being drawn correctly in kf5. Maybe this is related to how LO integrates with the system theme in KDE.
Comment 4 Michael Weghorn 2023-01-10 16:47:05 UTC
(In reply to Rafael Lima from comment #3)
> I'd say this is a duplicate of bug 150451. Although it complains about dark
> mode

Yes, sounds like a duplicate. Let's close this one and set bug 150451 to NEW.

*** This bug has been marked as a duplicate of bug 150451 ***