Closed Bug 1778204 Opened 3 years ago Closed 3 years ago

LightweightThemeChild doesn't call update() for non-sidebar parent process documents

Categories

(Firefox :: Theme, task)

task

Tracking

()

RESOLVED FIXED
104 Branch
Tracking Status
firefox104 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

Details

Attachments

(2 files)

This line here:

https://searchfox.org/mozilla-central/rev/d8225c5b4874325e3024a6857a65eb87e4d6fee9/browser/actors/LightweightThemeChild.jsm#39

assumes that if LightweightThemeChild is running in the parent process, that it's for a sidebar. That bit of gunk that I highlighted does the job for finding the root docShell outerWindowID if the document happens to be a sidebar, but ends up getting at the about:firefoxview outerWindowID for the about:firefoxview case.

We should make it so that LightweightThemeChild returns the outerWindowID of the top-level chrome window in either case.

Blocks: 1761782

The other mechanism was working fine for sidebars, but falls over as soon as we
have a normal browser running in the parent process in the main content area.

This will also be helpful if / when we decide to support themes in about:preferences,
about:config, and other parent-process pages.

Assignee: nobody → mconley
Status: NEW → ASSIGNED
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6ade0f685c46 More reliably get at the outerWindowID of the root window in LightweightConsumerChild.jsm. r=sclements,dthayer
Keywords: leave-open
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a616ef9e2944 Add a test for contentTheme for in-process tabs. r=dthayer
Keywords: leave-open
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: