Tables: Set simpler selectors to decrease specificity #39608
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.
Description
Re introduce v4 selectors.
Adapt the selectors accordingly so we can support
.table > tr > td
.Question that need to be answered:
.table > tbody.table-striped > tr:nth-of-type(odd) > *
.table > * > tr.table-sm > *
Motivation & Context
The actual specificity seems quite controversial and seems to be a bit too high.
Some tables implement simpler structures so with these selectors, it might be easier to handle these kind of tables.
Make the use of table selectors easier for everyone.
Keep the nested thing. It should be kept with the provided code.
Type of changes
Checklist
npm run lint
)Live previews
Related issues
Might close #34184.
Might supersede #34269.
Some commentary in much issues such as #38779 (comment)