Updates for Chrome 129 beta #24210
Merged
Updates for Chrome 129 beta #24210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:api 🐇
This was referenced Aug 23, 2024
chrisdavidmills
approved these changes
Aug 23, 2024
There was a problem hiding this comment.
@Elchi3 I've done my usual investigation of the features in the enabled list in the 129 roadmap. There is maybe one small item in the second section below that you could investigate for possible inclusion in the PR, but overall I think this looks fine.
Items included in the 129 roadmap that are in the PR
- Blob support in WebRTC data channels
- api.RTCDataChannel.binaryType.blob_value
- CSS interpolate-size property and calc-size() function
- css.properties.interpolate-size
- css.properties.interpolate-size.allow-keywords
- css.properties.interpolate-size.numeric-only
- css.types.calc-size
- Intl.DurationFormat
- javascript.builtins.Intl.DurationFormat
- javascript.builtins.Intl.DurationFormat.DurationFormat
- javascript.builtins.Intl.DurationFormat.format
- javascript.builtins.Intl.DurationFormat.formatToParts
- javascript.builtins.Intl.DurationFormat.resolvedOptions
- Rename inset-area to position-area
- api.CSSPositionTryDescriptors.position-area
- api.CSSPositionTryDescriptors.positionArea
- css.properties.position-area
- css.properties.position-area.block-end
- css.properties.position-area.block-start
- css.properties.position-area.bottom
- css.properties.position-area.center
- css.properties.position-area.end
- css.properties.position-area.inline-end
- css.properties.position-area.inline-start
- css.properties.position-area.left
- css.properties.position-area.none
- css.properties.position-area.right
- css.properties.position-area.self-end
- css.properties.position-area.self-start
- css.properties.position-area.span-all
- css.properties.position-area.span-block-end
- css.properties.position-area.span-block-start
- css.properties.position-area.span-bottom
- css.properties.position-area.span-end
- css.properties.position-area.span-inline-end
- css.properties.position-area.span-inline-start
- css.properties.position-area.span-start
- css.properties.position-area.span-top
- css.properties.position-area.span-x-end
- css.properties.position-area.span-x-start
- css.properties.position-area.span-y-end
- css.properties.position-area.span-y-start
- css.properties.position-area.start
- css.properties.position-area.top
- css.properties.position-area.x-end
- css.properties.position-area.x-self-end
- css.properties.position-area.x-self-start
- css.properties.position-area.x-start
- css.properties.position-area.y-end
- css.properties.position-area.y-self-end
- css.properties.position-area.y-self-start
- css.properties.position-area.y-start
- Web Authentication API: JSON serialization methods
- api.PublicKeyCredential.parseCreationOptionsFromJSON_static
- api.PublicKeyCredential.parseRequestOptionsFromJSON_static
- api.PublicKeyCredential.toJSON
Items included in the 129 roadmap that are not in the PR, but should be included
- scheduler.yield(): Ah, but I saw your note about it. Slipped to 130, @rachelandrew?
- WebGPU extended range (HDR) support: This is a
GPUCanvasContext.configure() config option, would the collector not pick that up?
Items included in the 129 roadmap that are not in the PR, and wouldn't be included
- Compute Pressure WebDriver extension commands
- CSS Anchor Positioning: Unwrapped inset-area(): I believe we dealt with this already, but the position-area BCD is not currently showing for some reason; needs to be investigated: https://developer.mozilla.org/en-US/docs/Web/CSS/position-area#browser_compatibility
- Private Aggregation API: client-side contribution merging
- Remove PointerEvent.getCoalescedEvents() from insecure contexts
- Snap Events
- Update CSS backdrop-filter to use mirror edgeMode
- Web Serial: connected attribute and RFCOMM connection events
|
I am told scheduler.yield will be in 129 but didn't go out with the 129 beta. I'm not sure why that happens. I guess we can check again before stable goes out and add it if it's there. |
|
Thanks Chris and Rachel! Merging this and further homework will be:
|
Merged
Yeah this missed the first 129 Beta cut but was added for the stable version. Raised #24439 to add it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The @openwebdocs BCD collector project v10.12.02 found new features shipping in Chrome 129 beta which was released yesterday. 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 52 features as shipping in Chrome 129:
See also the 129 "Enabled by default" column on https://chromestatus.com/roadmap.
Notes on features mentioned on chromestatus not listed here:
cc @chrisdavidmills @rachelandrew