I'm requesting a TAG review of an HTML layer attribute for the <link> tag.
One of the primary use-cases for CSS Cascade Layering is to manage the priority of third-party CSS (libraries and design systems) in relation to site-specific styles. It's currently possible to manage this layering on the CSS @import rule, as defined in CSS Cascading and Inheritance Level 5. However, there are many situations where authors do not want to use @import for performance reasons, or cannot use @import because of build tooling. Providing this functionality on the HTML <link> tag would bring it in better alignment with the CSS import functionality.
There seems to be broad consensus on this aspect of the feature, and I wanted to get formal review in order to hopefully move the conversation forward.
Major unresolved issues with or opposition to this design: The discussions have generally stalled in trying to provide an additional 'support' condition to stylesheet links, which I will split into a separate explainer.
This work is being funded by: Some of my work on the feature has been funded by Google Chrome
こんにちは TAG-さん!
I'm requesting a TAG review of an HTML
layerattribute for the<link>tag.One of the primary use-cases for CSS Cascade Layering is to manage the priority of third-party CSS (libraries and design systems) in relation to site-specific styles. It's currently possible to manage this layering on the CSS
@importrule, as defined in CSS Cascading and Inheritance Level 5. However, there are many situations where authors do not want to use@importfor performance reasons, or cannot use@importbecause of build tooling. Providing this functionality on the HTML<link>tag would bring it in better alignment with the CSS import functionality.There seems to be broad consensus on this aspect of the feature, and I wanted to get formal review in order to hopefully move the conversation forward.
Further details:
<link>to a cascade layer