[selectors-5]: Update heading specs based on resolutions in #10296 #12404
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
keithamus
force-pushed
the
update-heading-spec
branch
from
979cdd0 to
018a3ff
Compare
zcorpan
approved these changes
Jun 27, 2025
This was referenced Jun 27, 2025
|
While I don't object to specifying it due to the discussion of the specificity, we usually don't mention specificity of pseudo-classes unless it's different from that of a class, as that's the generic default behavior. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I merged #11836 a little hastily, as it does not reflect some of the resolutions we had in the WG meetings (#10296 (comment)), specifically:
:heading()can have comma separated An+B values, so needs to define a production that accommodates that. It now does.