On 5/16/22 11:05, Byungwoo Lee wrote:
Anticipated spec changesThere are 4 open issues posted on the csswg draft. * Remove scope dependency from relative selectors definition: https://github.com/w3c/csswg-drafts/issues/6399 * Disallowing logical combination pseudo classes inside ':has()': https://github.com/w3c/csswg-drafts/issues/6952 * Disallowing ':scope' inside ':has()': https://github.com/w3c/csswg-drafts/issues/7211 * Disallowing ':host', ':host()', ':host-context()' inside ':has()': https://github.com/w3c/csswg-drafts/issues/7212
It'd be great to get resolution on these issues before shipping, IMO.In general, given how the usefulness of this feature relies on browser engines having predictable performance (the feature is useless if WebKit or Firefox get cases fast that Chrome gets slow or vice-versa), it'd be great to document in the spec some of these limitations and the reasoning for them.
To be clear, in general I'd favor shipping with the limitations in place for now, and if/when there are use cases and so to unrestrict them do so. But that said, for that we need proper detection for those limitations. I filed this on the topic:
* https://github.com/w3c/csswg-drafts/issues/7280 -- Emilio -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a0c6192b-fa42-357b-4902-53d4d4bf75dc%40mozilla.com.
OpenPGP_0xE1152D0994E4BF8A.asc
Description: OpenPGP public key
