Disable dom.timeout.defer_during_load or make it disableable on a per-site basis
Categories
(Core :: Performance: General, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Keywords: webcompat:platform-bug)
User Story
platform:windows,mac,linux,android impact:site-broken configuration:general affects:all branch:release user-impact-score:200
Attachments
(1 file)
Bug 1270059 has caused a number of webcompat regresssions. It doesn't seem practical to rely on outreach to get these site bugs fixed. Given this, I'd say our options are:
- Disable it everywhere
- Make it possible to disable based on url via an intervention
My leaning is towards disabling it everwhere as that avoids us having to find, diagnose and ship interventions for issues. However, it would be good to get a sense of the performance benefit defer_during_load
gives us to know how much we'd be loosing.
Reporter | ||
Updated•1 month ago
|
Reporter | ||
Updated•1 month ago
|
Assignee | ||
Comment 1•1 month ago
|
||
Sites with racy code can sometimes fail if we don't run timeouts
immediately. Note that in most cases it will still be racy and can still
fail.
Updated•1 month ago
|
Comment 4•1 month ago
|
||
I'm looking into why browser_preferences_usage.js has started failing in Thunderbird and it's because IsURIInPrefList
is now being called a lot. It seems to me that a null principal would never be in a pref list, so IsURIInPrefList
could be short-circuited.
Assignee | ||
Comment 5•1 month ago
|
||
Links to data on the failures?
Agreed null principals wouldn't be in the pref list; we could check that before calling IsURIInPrefList, though the check could be out there too
Assignee | ||
Updated•1 month ago
|
Comment 6•1 month ago
|
||
Test failure: https://treeherder.mozilla.org/logviewer?job_id=500833291&repo=comm-central&lineNumber=17924
I've sent a patch in bug 1956233
Assignee | ||
Updated•1 month ago
|
Description
•