Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Add many missing CSS property values (added since ~2015) #28138

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

Open
queengooborg wants to merge 11 commits into main
base: main
Choose a base branch
Loading
from css/v7-values/since-2015

Conversation

Copy link
Contributor

@queengooborg queengooborg commented Oct 10, 2025 •
edited
Loading

This PR is a part of a process to add all of the missing spec-defined CSS property values. These values are added by the mdn-bcd-collector, following an upgrade of Webref CSS to v7 and directly parsing the syntax for each property.

This specific PR focuses on CSS property values that were added in browser versions after ~2012. This PR includes a combination of values added when the properties were introduced, as well as values added afterwards. Any values that didn't seem plausible were omitted. Spec URLs were obtained for as many values as possible.

Notes:

  • Chrome: Chrome 15+ was tested, with only a few versions that failed to be tested.
  • Firefox: Firefox 5 through 49 crashed during tests, so no results were obtained for those versions. Versions within this range were guesstimated by parent data, with the intent to fine-tune the version numbers later if needed.
  • Safari: Not all Safari versions were tested during this process (partially due to a lack of VM access), but test results were collected for every major Safari version. Specific minor versions were inferred by parent data, with the intent to fine-tune the version numbers later if needed.
  • (削除) Spec URLs: csswg.org went down frequently during the creation of this PR. Some spec URLs could not be obtained while the website was down. (削除ここまで) Spec URLs had been added later.
  • Properties with Prefixes/Alt. Names: If a property had a prefix or alternative name, and the collector reported that a value was supported in the first version that supported the standard name, then it was assumed that the value was supported from the beginning and had been updated accordingly.
  • isolation Property: Opera was set to a later version (Opera 30 = Chrome 43) than the matching Chrome version (Opera 28 = Chrome 41). Because Opera 30 was from the original wiki migration, it was replaced with mirroring.
  • block-size and inline-size Properties: Samsung Internet was set to 5.0, but in the PR that added it (Updating intrinsic sizing keywords data #3457 ), I found no supporting documentation for that version number. As such, to fix consistency, the data was treated as untrustworthy and replaced with mirroring.

@github-actions github-actions bot added data:css Compat data for CSS features. https://developer.mozilla.org/docs/Web/CSS size:xl [PR only] >1000 LoC changed labels Oct 10, 2025
Copy link
Contributor

github-actions bot commented Oct 10, 2025 •
edited
Loading

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

Copy link
Contributor

Will this change the baseline for any features? I'm also a little bit worried about how big this'll make some of the support tables, but that's probably fine. Nice work!

Copy link
Contributor Author

Thanks!

Theoretically, Baseline should not change for any of the features, since any features introduced in versions later than the base property itself would probably get a different tag. But we'll see when the Web Platform DX group tags them!

As for the table size, most of the properties shouldn't see their tables grow much, as only a handful of values are added. There are a few properties where a lot of values are added, but I think that they're all relevant to list!

Copy link
Contributor

@caugner caugner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and plausible to me overall.

I noticed that some spec URLs are missing though!?

Copy link
Contributor Author

Yeah, I mentioned the reason why lots of spec URLs were missing in the PR description:

Spec URLs: csswg.org went down frequently during the creation of this PR. Some spec URLs could not be obtained while the website was down.

I do intend to add them in, hopefully when I do, the CSSWG website will be fixed!
caugner reacted with heart emoji

Copy link
Contributor Author

Alright, got all the ones that I could track down added in! For any that are still not added, I was not able to find a link that was specific enough to the value, and wasn't sure if linking to the property instead would be good to do.

Copy link
Contributor

caugner commented Oct 16, 2025

Alright, got all the ones that I could track down added in! For any that are still not added, I was not able to find a link that was specific enough to the value, and wasn't sure if linking to the property instead would be good to do.

For the ones without specific fragment, it would be best to have a link to the property with a text fragment pointing to the value. In Firefox Nightly (not sure about stable), this works by first clicking on the property anchor link, then select the value, and select Copy link to selection from the right-click context menu.

@caugner caugner self-requested a review October 16, 2025 21:12
Copy link
Contributor Author

I didn't think we were allowing text fragments, but that makes sense! Alright, I'll get going on that and update this PR as soon as I can!

Copy link
Contributor Author

Alright, all missing spec URLs should be added now!
caugner reacted with heart emoji

},
"border-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-border-box",

},
"content-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-content-box",

},
"fill-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-fill-box",

},
"margin-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-margin-box",

},
"padding-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-padding-box",

},
"stroke-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-stroke-box",

},
"view-box": {
"__compat": {
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"spec_url": "https://drafts.fxtf.org/motion/#valdef-offset-path-offset-path--coord-box",
"spec_url": "https://www.w3.org/TR/css-box-4/#valdef-box-view-box",

"__compat": {
"mdn_url": "https://developer.mozilla.org/docs/Web/CSS/text-decoration",
"spec_url": [
"https://drafts.csswg.org/css-text-decor/#text-decoration-property",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update the spec URL for the property, to account for thickness values:

Suggested change
"https://drafts.csswg.org/css-text-decor-4/#text-decoration-property",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@caugner caugner caugner requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

data:css Compat data for CSS features. https://developer.mozilla.org/docs/Web/CSS size:xl [PR only] >1000 LoC changed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /