Closed Bug 306054 Opened 19 years ago Closed 19 years ago

Mozilla CSS extension to "post import"

Categories

(Core :: CSS Parsing and Computation, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: benjamin, Assigned: benjamin)

References

Details

For bug 305746 I would like an extension to Mozilla CSS which is like @import,
but it adds the imported style sheet to the cascade after the current style
sheet. Discussed briefly with bz on IRC, my proposed syntax is:

@-moz-post-import url();

I want to do this so that XUL can automatically import
chrome://global/content/xul.css which will do the default styles, and then
post-import chrome://global/skin/xul.css which will override theme-specific
styles as necessary. (Same idea for all our other stylesheets).

<bz> bsmedberg: would need to flag child sheets as coming after and modify the
walking code accordingly.
...
<bz> bsmedberg: how, if at all, should this be reflected in the CSSOM?
<bsmedberg> whew, I'm not sure
What's the advantage of doing:

@post-import url(b);

...RULES...

over doing:

@import url(a); /* contains ...RULES... */
@import url(b);

?
dbaron, mainly because it's an extra (third) CSS file for every one of our
current content/skin pairs. It's not a terrible solution, if this would be hard
to implement.
How many of these are you talking about?  Your initial comment mentioned just
xul.css.  Do you mean every CSS file in the skin, or every package, or something
else?
Oh, I guess you already said all of them, which makes sense.
Discussed further, and it seems a lot simpler to just have multiple import
statements from ua.css, and have XUL files with two <?xml-stylesheet?> declarations.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
OK, although if you decide you do want it *and it's reasonably simple to
implement*, it would be fine with me.  But I could imagine it being somewhat
complicated, in which case I'd be a bit hesitant.
You need to log in before you can comment on or make changes to this bug.