Skip to content

Conversation

@jamesnw
Copy link
Collaborator

@jamesnw jamesnw commented Sep 28, 2025

This doesn't impact any dates, and slots keys alongside existing keys. It does look like there are some anchor positioning keys missing Chrome support in BCD, for instance css.properties.position-area.top, but at least this will update when BCD gets updated.

@github-actions github-actions bot added the feature definition Creating or defining new features or groups of features. label Sep 28, 2025
Copy link
Contributor

@captainbrosset captainbrosset 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 to me, especially because no dates are changing.
Question for a possible follow-up PR: would any of these new BCD keys maybe represent a standalone feature we should be creating?

@jamesnw
Copy link
Collaborator Author

jamesnw commented Oct 1, 2025

Question for a possible follow-up PR: would any of these new BCD keys maybe represent a standalone feature we should be creating?

Not for alignment-baseline. For anchor positioning, I don't think we should split yet. I think once we know what exactly has been shipped as part of Interop and it reaches baseline, we should look at essentially locking the feature at what is interoperable at that point. Then there will likely be a handful of smaller features that will be added in the coming months.

@captainbrosset captainbrosset merged commit d39d184 into web-platform-dx:main Oct 2, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature definition Creating or defining new features or groups of features.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants