Clean up -webkit-background-clip data #4291
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.
This PR fixes a number of issues with the background-clip data. It was kind of a mess. This also contributes to #3804 and #3805.
Update
-webkit-background-clip
property data for WebKit and ChromiumWhile working on #4290, I found that
-webkit-background-clip
was added to WebKit at the same time asappearance
: https://trac.webkit.org/changeset/13874/webkitBecause this predates Chromium, I've set the
-webkit-background-clip
versionon Chromium and derived browsers to their first releases.
Since I was changing this data anyway, I also corrected the style of the notes, to refer to the browsers specifically (rather than WebKit generically).
Update
content-box
value data for ChromiumThis blog post on the WebKit post establishes that the
content-box
value was original to-webkit-background-clip
, so I updated the Chromiums accordingly: https://webkit.org/blog/164/background-clip-text/Clean up
text
value dataFirst, I cleaned up the version data itself:
text
value: https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/StandardCSSProperties.htmltext
value startedworking in Chrome 3: https://crbug.com/8872
Then I cleaned up the messy
prefix
data and notes. Mostly, I replacedprefix
data withpartial_implementation
to catch that apparently some browsers only allowtext
with the-webkit-
prefix on the property itself (not the value), or I removed the data where it didn't appear to be applicable. Since I was changing the notes, I also corrected for style, splitting the distinct notes into arrays.