[selectors-4] Update at-risk info for :has(), :read-write(), and :blank()
#8168
Labels
selectors-4
Current Work
Comments
This was referenced Dec 1, 2022
|
Yup, these all make sense to fix as we trim Selectors 4 for CR. |
|
It seems that |
SelenIT
added a commit
that referenced
this issue
Dec 17, 2022
Makes at-risk features list consistent with the Changes section according to the resolution of #8168
nt1m
pushed a commit
that referenced
this issue
Jan 11, 2023
Makes at-risk features list consistent with the Changes section according to the resolution of #8168
jakearchibald
pushed a commit
to jakearchibald/csswg-drafts
that referenced
this issue
Jan 16, 2023
Makes at-risk features list consistent with the Changes section according to the resolution of w3c#8168
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-writeis 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
:blankthat 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
The text was updated successfully, but these errors were encountered: