Repository navigation
[selectors-4] Update at-risk info for :has(), :read-write(), and :blank() #8168
Description
The features listed as at-risk in the document status section seem outdated.
Since :has() is now implemented in WebKit and Chromium, it probably shouldn't be marked as at-risk anymore.
Furthermore, :read-write is implemented in all main browser engines for a long time already. So I guess it can also be removed from the list.
And last but not least, there's a note under :blank that it's at-risk, there's still some discussion around it and there is no implementation so far, though it is currently not listed in the document status. So I believe it should definitely be added there.
Sebastian
Activity
tabatkins commentedon Dec 1, 2022
Yup, these all make sense to fix as we trim Selectors 4 for CR.
SelenIT commentedon Dec 14, 2022
It seems that
:has()and:read-writeare still in the at-risk list after merging the PR, is this intentional?Remove at-risk status from :has() and :read-write
Remove at-risk status from :has() and :read-write (#8242)
Remove at-risk status from :has() and :read-write (w3c#8242)