Closed
Bug 12106
Opened 25 years ago
Closed 25 years ago
XUL Overlays do not properly handle css files
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: hangas, Assigned: peterl-retired)
References
Details
XUL overlays should be able to include css files that impact the entire master xul document, and the overlay should be influenced by all the css files in the master document. Currently this is not working. tasksOverlay.xul and others are currently including xul.css and other css files in order for the xul within the overlay to inherit the necessary styles. Dave and I talked about this after I filed bug 10452 which has been closed. The problem remains so I am opening this bug to make the problem a little clearer.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
Comment 1•25 years ago
|
||
My hands have deteriorated to the point where I can no longer type. I need help. If you think you can fix this bug on your own, please take it away from me. If you'd like to volunteer to be my hands for a specific bug, then I'll be happy to come up to your cube and sit with you and fix the bug (assuming you have the patience for that).
Comment 3•25 years ago
|
||
this bug is a dup of a bug peterl has. see "style bug?" thread in layout to find out which one.
Updated•25 years ago
|
Assignee: hyatt → peterl
Status: ASSIGNED → NEW
Comment 4•25 years ago
|
||
Also reassigning to peterl. This is a dup of the style sheet ordering bug (where a rule in a later sheet blows away a more specific rule in an earlier sheet).
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12 → M11
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
Don't know about any overlay-specifc issues remaining (and no testcase here for overlays), but the sheet cascade order bug is fixed.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•