Closed Bug 1412182 Opened 7 years ago Closed 7 years ago

stylo: the stylo-blocklist is not effective when e10s is disabled

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox56 --- unaffected
firefox57 --- affected
firefox58 --- affected

People

(Reporter: xidorn, Unassigned)

References

Details

This is because when nsLayoutUtils::Initialize() is run in the parent process, the preferences are not yet read, while stylo blocklist depends on reading the pref there.

It seems that child process would have preferences before that function is called, so the blocklist is effective in child process.

I'm not sure how much do we care about stylo blocklist on non-e10s pages.
Chris, do you think this is something worth fixing?
Flags: needinfo?(cpeterson)
I don't think we need to fix this because e10s is expected to be the default for nearly all users in 57. The two issues blocking e10s everywhere are legacy add-ons (which will be dropped in 57) and Windows a11y (expected to ship in 57).
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56: --- → unaffected
status-firefox57: --- → affected
status-firefox-esr52: --- → unaffected
Flags: needinfo?(cpeterson)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.