-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unprefixed box-decoration-break
#723
Comments
Thank you for proposing Unprefixed We wanted to let you know that this proposal was not selected to be part of Interop this year. On behalf of the entire Interop team, thank you for submitting this proposal for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop. For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2025. Posted on behalf of the Interop team. |
Description
The
box-decoration-break
CSS property still needs a-webkit-
prefix in Chromium and WebKit. Chromium is currently working on shipping unprefixed support.There is currently an open pull request for WebKit, but some some major things still seem to be unimplemented. (see bug) See also: #702 (comment)
This issue is one of seven issues regarding unprefixing CSS properties/values, originally all in #702 (as per #702 (comment)). The aim is to group the properties together into multiple (but not seven) focus areas.
Specification
https://drafts.csswg.org/css-break-4/#break-decoration
Additional Signals
No response
The text was updated successfully, but these errors were encountered: