Closed
Bug 1631289
Opened 5 years ago
Closed 5 years ago
Stop including preferences.css twice in preferences dialogs
Categories
(Firefox :: Settings UI, defect, P3)
Firefox
Settings UI
Tracking
()
RESOLVED
FIXED
Firefox 77
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox75 | --- | unaffected |
| firefox76 | --- | unaffected |
| firefox77 | --- | fixed |
People
(Reporter: ntim, Assigned: ntim)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Some dialogs include preferences.css twice:
- Once by: https://searchfox.org/mozilla-central/rev/a4d62e09a4c46aef918667fa759bf9ae898dc258/browser/components/preferences/in-content/subdialogs.js#48
- Once by
<?xml-stylesheet href="chrome://browser/skin/preferences/preferences.css"?>, see https://searchfox.org/mozilla-central/search?q=preferences.css&case=false®exp=false&path=.xhtml
It's annoying for debugging styles, and I suspect it's not great for perf either (though probably negligible).
Comment 1•5 years ago
|
||
I believe the dialogs that include it in their markup do this because they may be opened outside of a subdialog. subdialogs.js should check that the stylesheet isn't already in the markup before injecting it.
Priority: -- → P3
| Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Has Regression Range: --- → yes
| Assignee | ||
Comment 3•5 years ago
|
||
Urgh, I'm really tired today.
| Assignee | ||
Updated•5 years ago
|
Status: REOPENED → NEW
| Assignee | ||
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → ntim.bugs
Status: NEW → ASSIGNED
Pushed by cbrindusan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fbce36fb761f
Stop including preferences.css twice in preferences dialogs. r=jaws
Comment 6•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago → 5 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 77
Updated•5 years ago
|
status-firefox75:
--- → unaffected
status-firefox76:
--- → unaffected
status-firefox-esr68:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•