[selectors-4] Move to CR?

[SebastianZ]

Given the huge list of features that are seem to be ready to release, I wonder whether we should try to get Selectors 4 in shape for moving to Candidate Recommendation status.

To do that, I suggest moving the following features to level 5 of the spec. and feature-freeze level 4:

• :local-link (already there, though needs to be removed from level 4)
• :interest-source and :interest-target
• :current
• :blank
• All grid-structural selectors, i.e. the || combinator, :nth-col(), and :nth-last-col()

@fantasai @tabatkins What's your opinion?

Sebastian

[svgeesus]

Stabilizing and feature-freezing seems like a good plan. Then:

• Update (and trim, for removed features) the changes section
• Add an (empty) Security Considerations
• Add WPT annotations for the relevant tests
• Republish a WD
• Get horizontal review
• Request CR

[fantasai]

I am in favor of this plan. Pushing Selectors 4 to CR is long overdue.

Are we proposing to defer :current(), :current() and :current, or all time-dimensional pseudo-classes?

[SebastianZ]

:past and :future already seem to be implemented in Chrome, Edge, Safari while :current (and :current()) is not, according to MDN. There are no WPTs to verify that, though.

Anyway, I wouldn't have a problem to defer all time-dimensional pseudo-classes if that helps avoiding controversies.

Sebastian

[fantasai]

FWIW, WebKit implements the resource state pseudo classes, so we may want to keep them if they are not riddled with issues.

[SebastianZ]

@fantasai Fine, I've removed the resource state pseudo classes from the list.

Adding Agenda+ to resolve on which features are moved to level 5.

Sebastian