- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 11 Feb 2026 16:37:21 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[cssom] CSSImportRule.media should be nullable, maybe? Difference between Chromium and Firefox`, and agreed to the following: * `RESOLVED: keep media on the @import rule object and see if it's web compat` <details><summary>The full IRC log of that discussion</summary> <ydaniv> emilio: the main thing here for @import and media is that it's a stylesheet and the main issue what happen if you don't load it<br> <ydaniv> ... one engine returns null, and another doesn't<br> <ydaniv> ... when you have @supports with media, should that be reflected in the interface?<br> <ydaniv> ... if we say no, then the answer for what the OM for @supports should do is pretty easy, provide whatever the rule has<br> <ydaniv> ... but what happen when there's no stylesheet<br> <ydaniv> ... and then file an issue in Blink for skipping rules entirely<br> <ydaniv> astearns: other opinions?<br> <emilio> should importRule.media == importRule.sheet.media<br> <ydaniv> astearns: what would be prefered resoluiton here?<br> <TabAtkins> Agree with emilio<br> <ydaniv> emilio: prefer if the media would be a part of the object<br> <ydaniv> ... but also it's incossistent with [missed]<br> <ydaniv> s/[missed]/it would make import incossitent with link<br> <emilio> <link media="foo"> -> StyleSheet.media mirrors `foo`<br> <ydaniv> dbaron: I guess media on the stylesheet is weird, it's not a charachter of the stylesheet, but of who imports it<br> <TabAtkins> +1 to dbaron, it's an odd legacy thing<br> <ydaniv> emilio: I think this is kinda what I proposed<br> <ydaniv> dbaron: do we want to keep it as is? or change what it does with new things?<br> <ydaniv> emilio: right now the media object in Gecko we deep clone them<br> <ydaniv> ... you could get stuff out of sync<br> <ydaniv> ... a bit edge case<br> <ydaniv> dbaron: for what it does it should be the same object or it gets out of sync, but do we want that behavior of not?<br> <ydaniv> emilio: there are compat implications, would like to try and see what ppl depend on<br> <ydaniv> PROPOSED RESOLUTION: keep media on the @import rule object and see if it's web compat<br> <dbaron> StyleSheet has ownerNode and CSSStyleSheet has ownerRule...<br> <ydaniv> emilio: the media on the stylesheet would return all and unconditionally imported would be a weird thing<br> <ydaniv> astearns: is it possible for stylesheet to have multiple ownerRules?<br> <ydaniv> ... emilio is proposed resolution good?<br> <ydaniv> emilio: I guess ok, specify they're the same object, so styleheet.meda and stylesheet.owner.media<br> <ydaniv> astearns: objections to proposed resolution?<br> <ydaniv> RESOLVED: keep media on the @import rule object and see if it's web compat<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12063#issuecomment-3885595259 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 February 2026 16:37:22 UTC