Consider reverting MBZ 1950995's system colour scheme override preference removal.

[RokeJulianLockhart]

Continues discussion of ≥ bugzilla.mozilla.org/show_bug.cgi?id=1950995#c6, where @K4sum1 stated:

I'm debating whether or not to revert https://bugzilla.mozilla.org/show_bug.cgi?id=1898096 in my fork r3dfox. (and by extension https://bugzilla.mozilla.org/show_bug.cgi?id=1952693, and https://bugzilla.mozilla.org/show_bug.cgi?id=1952328) It seems to break a lot of stuff, and made the colors funny. However I also don't know if it is entirely worth it or if I would want to maintain the changes on the long term once things (i hope) eventually get smoothed out.
I'd also revert this if it comes to happen, and at least look into https://bugzilla.mozilla.org/show_bug.cgi?id=1888225

So I'm going to let you decide what I do.

[the-r3dacted]

Well you kinda just quoted my post here so idk what to do?

[RokeJulianLockhart]

https://github.com/Eclipse-Community/r3dfox/issues/303#issuecomment-2952436396

Wanted to plonk it in a response. You were too fast!

https://github.com/Eclipse-Community/r3dfox/issues/303#issue-3126958537

@K4sum1, I'm not sure I can, in much good conscience, advise you to maintain a downstream patch, because I realise how much burden even a few modifications puts on maintenance when you ultimately don't want to hard fork.

However, I know that all of them together would be a significant factor in deciding whether to switch to this fork. If that's infeasible, note that id=1888225, for me, would be easily the most useful (although the other advocate in ≤ id=1950995#c4 probably would prioritise id=1950995).

[the-r3dacted]

If that's infeasible, note that id=1888225, for me, would be easily the most useful

I did some changes and I think I have most of the color issues corrected. Although one of the goals of my fork is to have a more native style theme (tickboxes, scrollbars, etc) and having a more native style settings would be that. However I'm not completely sure how to do it.

(although the other advocate in ≤ id=1950995#c4 probably would prioritise id=1950995).

I'd need to know how exactly it's not working to look into it.

[RokeJulianLockhart]

However I'm not completely sure how to do it.

@K4sum1, other than something like blog.chromium.org/2020/03/updates-to-form-controls-and-focus.html, I don't think that there's much you can do. I believe that both Gecko and Servo style HTML controls themselves, rather than delegate them to a toolkit. Even QtWebEngine just uses whatever Chromium provides, as WebKitGTK does with... WebKit.

I'd need to know how exactly it's not working to look into it.

cpe:/a:kde:plasma:6.3.5's kcmshell6 kcm_colors ¹ exposes a QPalette to ⪅ firefox-138.0.3 (via KColorScheme; it's a Qt-wide-compatible subset of what KDE Frameworks offers): ²

FF used to consume this, and expose it via about:preferences#general: ³

1. 

2. 

However, firefox-139.0 now doesn't. They must be hardcoded by the user from within FF's GUI:

1. 

2. 

Footnotes

1. plasma-workspace-libs-6.3.5-1.fc42.x86_64 ⁴ ↩

2. superuser.com/revisions/1895055/7 ↩

3. accessibility.blog.gov.uk/2016/05/26/accessibility-and-me-marian-foley ↩

4. discuss.kde.org/t/34220/6 ↩