Adds additional contain features and keys #2252
Open
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.
Adds a feature for the
contain
property itself, to include the higher level keywords valuesnone
,strict
, andcontent
which are either the default (no containment) or aliases for already included keyword values.The main key
css.properties.contain
is already included in a keyword feature. I'm not sure of the protocol for moving a key from one feature to another, but if thecontain
feature is accepted as-is, it should reclaim that key.Also adding keys to the
content-visibility
feature which required an updatecompute_from
to maintain consistent support reporting