Re: [csswg-drafts] [css-cascade] Provide an attribute for assigning a <link> to a cascade layer (#5853)

The CSS Working Group just discussed `Providing an attribute for providing a link to a cascade layer`.

<details><summary>The full IRC log of that discussion</summary>
&lt;myles> Topic: Providing an attribute for providing a link to a cascade layer<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/5853<br>
&lt;myles> miriam:  This might need to to HTML.<br>
&lt;argyle> https://www.irccloud.com/pastebin/zWOYuXvD/<br>
&lt;argyle> oh! full snippets!?<br>
&lt;myles> miriam: The idea is if we're able to import into a layer in a stylesheet, shoudl be able to do this from a link to a stylesheet? Like an attribute. But there are issues. Attributes are usually ignored if the browser doesn't support them. Then you'd get a different fallback behavior than if the browser ignored a layer block<br>
&lt;myles> florian: I dont' think that syntax can work. Doing it from HTML seems valid. but it probably couldn't be &lt;missed> it would have to be something else because of fallback .Maybe rel="layer"<br>
&lt;myles> florian: other than that, sure, why not<br>
&lt;myles> fremy: there's an attribute for media<br>
&lt;myles> fremy: we can maybe use it in have a special syntax: media="layer=..."<br>
&lt;myles> fremy: I dunno,t hat was a random thought. IN browsers which don't support layer, it would never match because this media doesn't exist<br>
&lt;myles> astearns: I'm not a fan of nesting it in media=<br>
&lt;myles> florian: It would be ugly but it would work.<br>
&lt;myles> astearns: For my clarification: florian, the layer attribute would not work, but just not in a link element, or also not in a style element<br>
&lt;myles> florian: if you have &lt;link> that loads a stylesheet that's ordinary in every respect except it also has a layer attribute, it wouldn't work because browsers would do a normal import, which isn't compatible behavior.<br>
&lt;myles> astearns: So it would also be a problem in &lt;style><br>
&lt;myles> miriam: The &lt;style> doesn't need this because you can just put a layer inside of it easily.<br>
&lt;myles> fantasai: We should table this until we have a specific proposal<br>
&lt;myles> florian: Or push to WHATWG<br>
&lt;bkardell_> you could &lt;style>@import ... right?<br>
&lt;myles> TabAtkins: let's open an issue on WHATWG.<br>
&lt;tantek> sounds reasonable<br>
&lt;myles> TabAtkins: Mabye we can stash it in media= like fremy said. They can think about it in WHATWG<br>
&lt;myles> astearns: ok.<br>
&lt;fantasai> +1 bkardell_, this might not be worth solving in HTML<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5853#issuecomment-777873541 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 11 February 2021 23:54:03 UTC