-
Notifications
You must be signed in to change notification settings - Fork 713
[css-2025] Add features to Safe to Release pre-CR Exceptions #10687
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
Comments
Yes we absolutely need a FPWD :) also it would be good if the spec had WPT annoutations to show how well it is tested |
In general, if the proposal for pre-CR exceptions is "all from spec foo" then it kind of implies that foo should move to CR. |
Agree, though some of them have a lot of open issues (in-spec and/or on GitHub), but all of their features are widely implemented. Not sure how to handle those. I'll try to dig up some numbers, so we can get a better picture of their actual state, though that'll take a bit. Sebastian |
To keep this issue up to date, the FPWD of CSS Easing 2 was published 29 August 2024 and I did add the WPT annotations. |
We still don't have a FPWD yet. |
I have now updated the list of features and added additional information and stats to them. The info on some of them is still incomplete and I'll continue updating it. Sebastian |
|
There is a question on whether we should include |
The FPWD of Easing 2 ws published 29 August 2024 and includes WPT annotations |
You already mentioned that earlier.😃 Sebastian |
I've updated "font-tech() and font-format() from CSS Conditional 5", "linear() from CSS Easing 2", "env(safe-area-inset-*) from CSS Environment Variables 1", and "All from CSS Highlight API 1". Sebastian |
Updated "conic-gradient() and for gradient functions from CSS Images 4", "text-box-trim and text-box-edge from CSS Inline Layout 3", and "All from CSS Overflow 3". Sebastian |
Updated "All from CSS Overflow 3", "All from CSS Paged Media 3" (though now wondering a bit whether really all should be added), "Typographic pseudo-elements, ::before, ::after from CSS Pseudo-Elements 4", and "text-decoration-thickness, text-underline-offset properties and from-font value for text-underline-position from CSS Text Decorations 4". Sebastian |
Updated the rest and included additional WPT and issues info. Sebastian |
Here's a (very hand-wavy) list of features I believe could be added to the "Safe to Release pre-CR Exceptions" section of CSS 2024:
All from CSS Animations 2
font-tech()
andfont-format()
from CSS Conditional 5font-format()
,font-tech()
): Chrome: 11, Edge: 11, Firefox: 11, Safari: 11; interop: 11 / 11 (100%)linear()
from CSS Easing 2env(safe-area-inset-*)
from CSS Environment Variables 1All from CSS Highlight API 1
conic-gradient()
and<color-interpolation-method>
for gradient functions from CSS Images 4text-box-trim
andtext-box-edge
from CSS Inline Layout 3All from CSS Overflow 3
All from CSS Paged Media 3
Typographic pseudo-elements,
::before
,::after
from CSS Pseudo-Elements 4 (basically all from CSS 2 with double-colon syntax plus::prefix
and::postfix
):is()
,:where()
,:has()
, and selector lists in:not()
from Selectors 4text-decoration-thickness
,text-underline-offset
properties andfrom-font
value fortext-underline-position
from CSS Text Decorations 4transition-behavior
property,@starting-style
rule andCSSStartingStyleRule
interface of CSS Transitions 2accent-color
property,auto
value foroutline-color
property, and<url-set>
value for thecursor
property from CSS UI 4Several of the interfaces defined in CSSOM 1
(I believe should be cut now regarding its feature set and a CSSOM 2 spec. started for new features, see #10686.)
For this list I went through all the specs and checked what seems fairly stable to me based on issues within the spec. and on GitHub and/or is already widely implemented in browsers. For some I checked the WPT coverage, though not all. I may go through them and provide some more detailed info. And there are surely some Interop 2023 and 2024 features I didn't list here yet, which might be added.
Everyone is encouraged to edit this list or suggest additions, changes, or removals! And let me know if it makes sense to split it into separate issues to discuss them individually!
Sebastian
The text was updated successfully, but these errors were encountered: