Hi Steiner,
I spent quite a lot of time trying to understand the issues around
nesting syntax. It looks like the CSSWG resolved to adopt "Option 3",
with representatives from all 3 engines voting in favor - and the WebKit
blog survey also resulted in "Option 3" as the top choice.
Do we know if the other engines have started work on implementation of
Option 3?
thanks,
Mike
On 1/20/23 4:42 AM, 'Steinar H. Gunderson' via blink-dev wrote:
> Contact emails: se...@chromium.org, fut...@chromium.org
> Explainer: None
>
> Specification: https://drafts.csswg.org/css-nesting
>
> Summary: Add the ability to nest CSS style rules inside other style rules,
> combining selectors from the outer with the inner rule for increasing
> modularity and maintainability of style sheets.
>
> Blink component: Blink>CSS
>
> TAG review: https://github.com/w3ctag/design-reviews/issues/791
>
> TAG review status: Pending
>
> Risks: There is a threat of a formal objection in CSSWG.
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/be91b584-f0ba-cd60-a142-f60c3aa72709%40chromium.org.
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/Y8ph9gk50U2D92f3%40google.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYckGUc%3DxjifpXRrOi_UQ2SCXO%2B68GuDAT4r0B%2B8qC4WSw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8gz3jMDHJHDiNtuhA3S2bQ7j30WJirJ%3DWCevpxCpEivw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/579baa85-3561-9614-102b-a20ae14a9fdf%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY_GfAW6OMy%3DV1ziiqSR2Qrs405KN8nd%2BBzF%3DHb8pqisFg%40mail.gmail.com.
You received this message because you are subscribed to a topic in the Google Groups "blink-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/blink-dev/eFCrkiLynfU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/32a43824-1b71-4b67-b1ce-05c4e9b1fc7dn%40chromium.org.
OTOH: Will authors actually need to feature detect this? I mean, feature detection won’t make a difference to visitors as it will have the same net outcome to them: the nested styles will not be applied in browsers that don’t support nesting. Only difference is that the parser might need to parse a bunch of extra things instead of being able to discard entire blocks upfront.