Updates: - Ensured that preload scanner picks up layered @import rules in <style> elements, with tests added (crrev.com/c/3321438) - I've also filed a WebKit issue for it ( https://bugs.webkit.org/show_bug.cgi?id=234094) - https://github.com/w3c/csswg-drafts/issues/6872 has been addressed and closed
On Thu, Dec 9, 2021 at 7:37 AM Emilio Cobos Álvarez <emi...@mozilla.com> wrote: > I would love if we could at least get: > > https://github.com/w3c/csswg-drafts/issues/6872 > > clarified and resolved. The behavior Chromium currently implements might > be what we want to end up doing, but that doesn't match the spec at all, > afaict. > > -- Emilio > > On 12/7/21 21:42, Xiaocheng Hu wrote: > > > > Contact emails > > > > xiaoche...@chromium.org <mailto:xiaoche...@chromium.org> > > > > > > Explainer > > > > https://gist.github.com/xiaochengh/58c793e3bf06a1bb0f7d472ebb170feb > > <https://gist.github.com/xiaochengh/58c793e3bf06a1bb0f7d472ebb170feb> > > > > > > Specification > > > > https://drafts.csswg.org/css-cascade-5/#layering > > <https://drafts.csswg.org/css-cascade-5/#layering> > > > > > > Design docs > > > > > > https://bit.ly/2SGjPlu <https://bit.ly/2SGjPlu> > > > > > > Summary > > > > CSS cascade layers (@layer rule and layered @import syntax) provide a > > structured way to organize and balance concerns within a single origin. > > Rules within a single cascade layer cascade together without > > interleaving with style rules outside the layer. This allows authors to > > achieve a certain cascade ordering for same-origin rules in a proper way. > > > > > > > > Blink component > > > > Blink>CSS > > < > https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> > > > > > > Search tags > > > > css <https://chromestatus.com/features#tags:css>, cascade > > <https://chromestatus.com/features#tags:cascade>, layer > > <https://chromestatus.com/features#tags:layer>, cascade-layer > > <https://chromestatus.com/features#tags:cascade-layer> > > > > > > TAG review > > > > https://github.com/w3ctag/design-reviews/issues/597 > > <https://github.com/w3ctag/design-reviews/issues/597> > > > > > > TAG review status > > > > Issues addressed > > > > > > Risks > > > > > > > > Interoperability and Compatibility > > > > As a new feature, there is no compatibility risk. Interoperability risk > > is very low as WebKit and Gecko are also actively developing this new > > feature. > > > > > > > > Gecko: In development > > (https://bugzilla.mozilla.org/show_bug.cgi?id=1699215 > > <https://bugzilla.mozilla.org/show_bug.cgi?id=1699215>) > > > > WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=220779 > > <https://bugs.webkit.org/show_bug.cgi?id=220779>) > > > > Web developers: Strongly positive > > (https://bugs.chromium.org/p/chromium/issues/detail?id=1095765 > > <https://bugs.chromium.org/p/chromium/issues/detail?id=1095765>) > > > > Other signals: > > > > > > Debuggability > > > > @layer rules will be surfaced to DevTools in the Style panel to indicate > > which layer the style rules are in. See crbug.com/1240596 > > <http://crbug.com/1240596> > > > > > > > > Is this feature fully tested by web-platform-tests > > < > https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md > >? > > > > Yes > > > > > > Flag name > > > > chrome://flags/#enable-cascade-layers > > > > > > Requires code in //chrome? > > > > False > > > > > > Tracking bug > > > > https://bugs.chromium.org/p/chromium/issues/detail?id=1095765 > > <https://bugs.chromium.org/p/chromium/issues/detail?id=1095765> > > > > > > Estimated milestones > > > > 99 > > > > > > > > Link to entry on the Chrome Platform Status > > > > https://chromestatus.com/feature/5663362835808256 > > <https://chromestatus.com/feature/5663362835808256> > > > > > > Links to previous Intent discussions > > > > Intent to prototype: > > > https://groups.google.com/a/chromium.org/g/blink-dev/c/chiJ2GIECPc/m/sIF9pfsdAAAJ > < > https://groups.google.com/a/chromium.org/g/blink-dev/c/chiJ2GIECPc/m/sIF9pfsdAAAJ > > > > > > > > This intent message was generated by Chrome Platform Status > > <https://www.chromestatus.com/>. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "blink-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to blink-dev+unsubscr...@chromium.org > > <mailto:blink-dev+unsubscr...@chromium.org>. > > To view this discussion on the web visit > > > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGha5qBJvcSa%2Bzs525XU8HBdpHhH1W3%3D9x%3DNrHnaSP6XTvg%40mail.gmail.com > < > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGha5qBJvcSa%2Bzs525XU8HBdpHhH1W3%3D9x%3DNrHnaSP6XTvg%40mail.gmail.com?utm_medium=email&utm_source=footer > >. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/15733bbb-2514-381a-35ee-b6a8a79f48e9%40mozilla.com > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGhbz_s-jOnF0jfbV6FiMcja15SAUzX9p3LaQ89eyKpevJg%40mail.gmail.com.
