Implement nsXPLookAndFeel::SetIntCacheImpl and GetIntCacheImpl for GTK
Categories
(Core :: Widget: Gtk, enhancement)
Tracking
()
People
(Reporter: jld, Unassigned)
References
Details
Comment 1•5 years ago
|
||
I did add the function in bug 1560660. Are there still something we need to do specifically?
Comment 2•5 years ago
|
||
It looks like that only remotes the dark theme info?
We probably need all the look and feel data from the parent to color things correctly in the children:
https://searchfox.org/mozilla-central/source/widget/gtk/nsLookAndFeel.h#45
On the other hand Bug 1381938 does away with native theming altogether (not enabled by default yet on Linux), so there question may be how much of the "native" theme styling we're still going to try to emulate past that point.
Updated•4 years ago
|
Comment 3•4 years ago
|
||
@ Cameron, do we still need this GTK LookAndFeel IntCache bug now that you moved the LookAndFeel data to the parent process in bug 1470983?
Comment 4•4 years ago
|
||
Setting Fission Milestone = ? until we determine whether we need to fix this bug to remove all X11 from the content process (bug 1129492) for Fission MVP.
Comment 5•4 years ago
|
||
Jed, do we still need this GTK LookAndFeel IntCache bug now that heycam moved the LookAndFeel data to the parent process in bug 1470983?
Comment 6•4 years ago
|
||
Has this code been rewritten since this bug was filed two years ago? The only reference I see to any SetIntCache or GetIntCache functions in mozilla-central are some old macOS comments about LookAndFeel::SetIntCache:
Comment 7•4 years ago
|
||
Yes, this code was rewritten a bit in bug 1657401, and I think that plus bug 1470983 covered all of the work that was going to happen here.
Reporter | ||
Comment 8•4 years ago
|
||
As comment 1 indicates, the task described in the bug summary was done in late 2019 as part of bug 1560660 (for non-sandbox-related reasons). When I filed this bug I didn't know much about nsLookAndFeel
or the extent of the cache mechanism; after I started investigating for bug 1470983 I eventually decided on a different approach.
Updated•4 years ago
|
Description
•