Deduplicate css.types.basic-shape.path
and descendants
#24502
Merged
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.
Summary
css.types.basic-shape.path
is shown as partially implemented in all browsers, but this information is a summation of the descendant features. This PR undoes this flattening, showingpath()
support commencing with the first of the subfeatures.Test results and supporting details
Since this is duplicate information, the source is BCD itself (i.e.,
css.types.basic-shape.path.{clip-path,d,offset-path,shape-outside}
), though I'm just deleting data rather than introducing new facts.The existing structure of this data—with subfeatures reiterating a partial implementation of the parent—makes actually consuming this data in web-features impossible. Because the parent feature is shown as not implemented and compute-baseline follows a feature's ancestry (e.g., to know if a feature is behind its parent's prefix), the descendants are also treated as partially implemented. Since there's a way to know which contexts are supported—the features dedicated to those facts—I think we shouldn't show partially implemented on the top-most
path()
feature.Related issues
web-platform-dx/web-features#1799