-
Notifications
You must be signed in to change notification settings - Fork 199
Adds additional contain features and keys #2252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jamesnw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor changes, but looks good!
Co-authored-by: James Stuckey Weber <jamesnw@gmail.com>
features/content-visibility.yml.dist
Outdated
| status: | ||
| baseline: low | ||
| baseline_low_date: 2024-09-16 | ||
| baseline: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're regressing the status, would you add a comment to the authored yaml file with a note as in #1973?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should no longer be a regression with mdn/browser-compat-data#25186 in 5.6.19.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are now no status changes here.
Adds a feature for the
containproperty itself, to include the higher level keywords valuesnone,strict, andcontentwhich are either the default (no containment) or aliases for already included keyword values.The main key
css.properties.containis already included in a keyword feature. I'm not sure of the protocol for moving a key from one feature to another, but if thecontainfeature is accepted as-is, it should reclaim that key.Also adding keys to the
content-visibilityfeature which required an updatecompute_fromto maintain consistent support reporting