Open
Bug 183038
Opened 22 years ago
Updated 2 years ago
CSSOM creation of @import rules messes up sheet ordering
Categories
(Core :: CSS Parsing and Computation, defect, P4)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: bzbarsky, Unassigned)
References
Details
(4 keywords)
Attachments
(1 file)
586 bytes,
text/html
|
Details |
This is spun off bug 107567. I'll try to attach testcases later tonight.
The right approach may be to make the @import rule kick off the child sheet load
upon being inserted into the parent sheet like we do for <link> and <style>.
No longer blocks: 107567
Blocks: 107567
Updated•22 years ago
|
Whiteboard: [whitebox]
Reporter | ||
Comment 1•22 years ago
|
||
Updated•22 years ago
|
Priority: -- → P2
Reporter | ||
Comment 2•22 years ago
|
||
Please do _NOT_ set the priority on my bugs. I can do it myself, thank you.
Priority: P2 → --
Reporter | ||
Updated•22 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla1.5beta
Reporter | ||
Comment 3•22 years ago
|
||
Another option, now that bug 98765 is fixed, is to push all the order-checking
and such down into the parser, eliminate this business of passing back an
nsISupportsArray, and change the appending function in this case to insert the
rule into the sheet in the right place.
Updated•21 years ago
|
QA Contact: ian → style-system
Reporter | ||
Updated•14 years ago
|
Assignee: bzbarsky → nobody
Keywords: helpwanted,
student-project
Priority: P2 → --
Target Milestone: mozilla1.5beta → ---
Priority: -- → P4
Reporter | ||
Comment 4•13 years ago
|
||
This is still an issue. See the comment right above mozilla::css::Loader::InsertChildSheet which explains the problem pretty clearly.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•