-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Updates for Chrome 120 beta #21148
Updates for Chrome 120 beta #21148
Conversation
Thanks for this @Elchi3. I would be happy to help review these PRs, and think they would be useful in several ways. For example, it would help me to do my BCD updates more quickly (by doing some of my work or me), and I could also use this as an forcing function to update my future work list, taking some of that burden off @rachelandrew's hands. The way I see it, in each case I would:
Does this sound like a good plan to y'all? Am I missing anything? |
Just a note to say you don't need to check the blog post, it's much easier to look at the Chrome Status roadmap as that's where the info from the post comes from. |
I am working on a script that classifies the list of features changed (like the one given by Florian in the OP) by spec. To test, I ran that list in it and got what follows (feedback welcome) Credential Management Level 1
HTML Standard
Intersection Observer
URL Standard
WebGPU
CSS 2
CSS Color Module Level 5
CSS Masking Module Level 1
CSS Values and Units Module Level 4
|
Thanks for your feedback, Chris! Glad this project is useful to y'all. It does sound like a good plan. As Rachel says, the https://chromestatus.com/roadmap is even easier to look at. In order to move forward with this PR, I would propose two things for you:
Thanks again for your help! |
HI! I'm working to link the Chromestatus features to the different BCD IDs. This should help @chrisdavidmills to find the Chromestatus entry related to what the collector has detected. Here is the current output. Feedback welcome! Note the section at the end (hidden by default) with the list of CS features not linked to spec with BCD IDs modified. Note: Official ChromeStatus roadmap for Chrome 120 Note: Official ChromeStatus [roadmap for Chrome 120](https://chromestatus.com/roadmap?120) Credential Management Level 1
HTML Standard
Potential ChromeStatus features:
Intersection Observer
Potential ChromeStatus features: URL Standard
WebGPU
Potential ChromeStatus features: CSS Color Module Level 5
CSS Masking Module Level 1
Potential ChromeStatus features: CSS Values and Units Module Level 4
Potential ChromeStatus features: Media Queries Level 5
Potential ChromeStatus features: ChromeStatus features not linked to one of these specs
The following BCD IDs have already been updated
|
OK, here is my review of all this stuff. Let me know if you think this is useful. Notes:
Items listed in the PR
Notes
Items in 120 roadmap, not listed in PR
Items listed in 120 roadmap that don't appear to be implemented or enabled
Items that seem to be supported, but I'm not sure how to represent in BCD
|
I'm taking care of css.selectors.dir in #21245. |
Thanks Chris! This is amazing and helps us a lot! I'm particularly interested in the "Items in 120 roadmap, not listed in PR" list which has 42 entries for which the collector can't currently add the features automatically for a few reasons:
I had forgotten CloseWatcher and Login API. The collector actually found them! So these are sorted and that means 27 entries can be added to BCD automatically thanks to this PR (and 42 of them can't, sorry, we will improve). |
That said, this PR proposes 27 features as shipping in Chrome 120 and they are confirmed by the chromestatus entries given above and by the collector tests. Please merge and the rest will have to be sorted separately.
|
All of the other `mask-` properties were unprefixed at the same time, only this one was left unmodified. I think this was missed in the course of running automatic updates for Chrome 120. See: mdn#21148 (comment)
The longhand properties were updated here: mdn#21148 Because the shorthand was recognized but had no effect, the collector couldn't detect this change. Supporting evidence: https://chromestatus.com/feature/5839739127332864
The longhand properties were updated here: #21148 Because the shorthand was recognized but had no effect, the collector couldn't detect this change. Supporting evidence: https://chromestatus.com/feature/5839739127332864
This data can't be mirrored, and so was missed in mdn#21148.
This PR is an experiment. I've run Open Web Docs' BCD collector against Chrome 120 which reached beta yesterday. We believe that when there are beta versions of browsers available it is a good time to update BCD and ideally we should do so automatically with the help of tooling. So today is the day when such a PR would be created in the cycle. I'm creating this PR manually for the moment, but in the future we hope it can be generated from a workflow.
The collector found 21 new features shipping in Chrome 120:
We can now compare this list against the blog post that @rachelandrew published and see if we have missed things and why (or if the blog posts missed things :)). https://developer.chrome.com/blog/chrome-120-beta/
Also cc'ing @chrisdavidmills who usually works on Chrome updates. Chris, if this PR would be auto-generated, would that be reviewable for you? What would you improve? Thanks for your input which will be useful for us as we design an automated workflow here. For more information about this project, see: openwebdocs/project#168