Closed
Bug 183505
Opened 23 years ago
Closed 20 years ago
XUL fastload messes up loading stylesheets
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
VERIFIED
FIXED
People
(Reporter: bzbarsky, Unassigned)
References
Details
When fastloading a document, we load stylesheets via AddPrototypeSheets() from
nsXULDocument::ResumeWalk(). This uses LoadAgentSheet which messes up some
things (like setting the right ownerNode on the sheet, using the right charset,
etc).
If the only issue is that we need sync loading, perhaps a sync version of
LoadStyleLink would be more appropriate here?
Comment 2•20 years ago
|
||
This depends on bug 319654, since the owner node should be the PI that referenced the stylesheet (in case the stylesheet is loaded because of a PI).
What about style overlays from the chrome registry? Is there a better way to load them than what we do now?
| Reporter | ||
Comment 3•20 years ago
|
||
Don't know much about style overlays, sorry... :(
Comment 4•20 years ago
|
||
bz explained on IRC that his concern was about stylesheets loaded from processing instructions - they were loaded differently in the fastload case than in normal one. In case of chrome registry style overlays we can't do anything better, as there's no node or charset to use.
Comment 5•20 years ago
|
||
Should be fixed by the patch in bug 319654.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•