-
Notifications
You must be signed in to change notification settings - Fork 27
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
Carryover evaluation: Color Spaces and Functions #457
Comments
Something to consider if we continue this focus area is whether we should fold #426 into it. |
A look through the unlabeled tests might also turn up valuable tests in case of scope expansion. |
That would make sense: Relative Color Syntax is now shipping in WebKit, being currently implemented in Blink and Mozilla has a favourable standards position and estimates implementation starting soon. WPT for `currentColor in Relative Color Syntax were also recently added (the desired behavior is specc'ed and implementations agree, but currently fail those tests). |
I'd strongly prefer to add things that are basically new features to new focus areas rather than adding additional scope to existing focus areas. There are two reasons for this:
I think extending focus areas only really makes sense where there are more tests for basically the same scope (e.g. adding new tests for flexbox or grid that still cover the same feature, just with additional coverage, as we did last year). |
That seems very reasonable to me. And current WPT results for RCS would show a nice improvement from this starting position: |
I was pointed in this direction. I’m not sure if this is exactly the right place but … ☞ https://bugs.webkit.org/show_bug.cgi?id=255939 |
Let's evaluate whether to continue the Color Spaces and Functions focus area in Interop 2024.
Original proposals:
Tests:
We should also consider whether we should add tests for 2024.
The text was updated successfully, but these errors were encountered: