Bug 489970 - The Restore Down button on Firefox (flatpak) can't be seen in dark mode
Summary: The Restore Down button on Firefox (flatpak) can't be seen in dark mode
Status: RESOLVED DUPLICATE of bug 416353
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-09 10:58 UTC by Omar Eldahan
Modified: 2024-09-18 16:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of Firefox with Restore Down dark and not visible (251.76 KB, image/png)
2024-07-09 10:58 UTC, Omar Eldahan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Omar Eldahan 2024-07-09 10:58:26 UTC
Created attachment 171497 [details]
Screenshot of Firefox with Restore Down dark and not visible

SUMMARY
The Restore Down button on Firefox (flatpak) can't be seen in dark mode. I am using KDE Plasma 6.1.1 (Wayland) on Fedora 40. This issue first appeared after upgrading from v6.0 to v6.1. Sometimes all of the buttons can't be seen (Minimize, Restore Down, and Close) however this usually goes away after rebooting. I don't know why or when they go dark and cannot replicate it, but it only happens occasionally. However, the Restore Down Button is always dark.

If the Firefox window isn't selected or active, you can see all of the buttons normally, but as soon as it's brought into focus, you can't see it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 40 (Workstation Edition) x86_64
KDE Plasma Version: KDE Plasma 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2-1.fc40
Comment 1 cwo 2024-09-18 16:01:20 UTC
Thank you for the bug report! There is another bug report open about miscolored unmaximize buttons for gtk apps; While that bug is technically refrencing light themes, I suspect it is the same issue. That report also seems to contain a workaround that you could try if you are affected by this issue.

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