-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Updates for Chrome 142 beta #28073
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 142 beta #28073
Conversation
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, yet the Navigation API collector tests pass in Chrome 141 for me (but not the test for api.SVGScriptElement.async
):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://chromestatus.com/feature/5134734612496384 confirms that Navigation API precommit handlers shipped in Chrome 141.
The @openwebdocs BCD collector project v10.15.1 found new features shipping in Chrome 142 beta which was released today. Currently, the collector covers about 90% of BCD, so the following list might not be exhaustive. Also, if a feature is in Chrome Canary/behind origin trials/enrollment, it is not considered here.
With this PR, BCD considers the following 33 features as shipping in Chrome 142:
Marked for Chrome 142 in other PRs:
Notes:
font-language-override
but it only got an intent to ship quite late so maybe it will be in a later beta for 142, or it will be in 143. https://groups.google.com/a/chromium.org/g/blink-dev/c/UNoijyJrMmE/m/5-taIHTCAgAJ. It is not supported in the 142 beta I used.interestfor
attribute is missing, the collector doesn't know about it because the spec is not yet merged. Add theinterestfor
attribute whatwg/html#11006. Other parts of this API have a spec and are included in this PR.See also the 142 "Enabled by default" column on https://chromestatus.com/roadmap and https://developer.chrome.com/blog/chrome-142-beta