Updates for Chrome 122 beta #21998
Merged
Updates for Chrome 122 beta #21998
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 🐇
Elchi3
commented
Jan 25, 2024
There was a problem hiding this comment.
@Elchi3 I checked the features added in this PR against the features listed as enabled in Chrome 122 beta release (see https://chromestatus.com/roadmap), and this is what I found:
Found by the collector and listed as enabled in the 122 beta
- Feature: FedCM: disconnect
api.IdentityCredential.disconnect_static
- Feature: Iterator helpers
javascript.builtins.Iterator.Iteratorjavascript.builtins.Iterator.dropjavascript.builtins.Iterator.everyjavascript.builtins.Iterator.filterjavascript.builtins.Iterator.findjavascript.builtins.Iterator.flatMapjavascript.builtins.Iterator.forEachjavascript.builtins.Iterator.fromjavascript.builtins.Iterator.mapjavascript.builtins.Iterator.reducejavascript.builtins.Iterator.somejavascript.builtins.Iterator.takejavascript.builtins.Iterator.toArray
- Feature: Set methods
javascript.builtins.Set.differencejavascript.builtins.Set.intersectionjavascript.builtins.Set.isDisjointFromjavascript.builtins.Set.isSubsetOfjavascript.builtins.Set.isSupersetOfjavascript.builtins.Set.symmetricDifferencejavascript.builtins.Set.union
- Feature: Storage Buckets API
api.Navigator.storageBucketsapi.StorageBucketapi.StorageBucket.cachesapi.StorageBucket.estimateapi.StorageBucket.expiresapi.StorageBucket.getDirectoryapi.StorageBucket.indexedDBapi.StorageBucket.nameapi.StorageBucket.persistapi.StorageBucket.persistedapi.StorageBucket.setExpiresapi.StorageBucketManagerapi.StorageBucketManager.deleteapi.StorageBucketManager.keysapi.StorageBucketManager.openapi.WorkerNavigator.storageBuckets
- Feature: URLPattern: hasRegExpGroups
api.URLPattern.hasRegExpGroups
- Feature: WebGL drawingBufferStorage
api.WebGL2RenderingContext.drawingBufferFormatapi.WebGL2RenderingContext.drawingBufferStorageapi.WebGLRenderingContext.drawingBufferFormatapi.WebGLRenderingContext.drawingBufferStorage
Found by the collector, but not listed in the 122 beta list
css.types.color.rgb.mixed_type_parameters(not in this PR but added to BCD manually previously)css.types.color.rgba.mixed_type_parameters(ditto)
Not found by the collector
- Allow setting IDP login status from same-site subresources: This doesn't sound like something that would be automatically detected anyway. It would be added as a manual sub-feature on api.NavigatorLogin.setStatus
- Feature: Async Clipboard API: Read unsanitized HTML: New
unsanitizedoption for api.Clipboard.read; would need to be added manually as a subfeature - Feature: Back/forward cache NotRestoredReason API: I'm pretty sure this is already added to BCD (api.PerformanceNavigationTiming.notRestoredReasons) from when I attempted to document it a while ago
- Feature: CSS @container with unsupported Features never match: New behavior for
css.at-rules.container; should be manually added as a subfeature - Feature: CSS Pseudo Element ::backdrop inheriting from Originating Element: New behavior for
css.selectors.backdrop; should be manually added as a subfeature - Feature: Do not delete File kind objects in dataTransfer.clearData(): New behavior for
api.DataTransfer.clearData; should be manually added as a subfeature - Feature: Interoperable mousedown event cancellation in iframe: New behavior for
api.Element.mousedown_event; should be manually added as a subfeature - Feature: RTCRtpSender setParameters() extensions for requesting the generation of a key frame: New behavior for
api.RTCRtpSender.setParameters; should be manually added as a subfeature - Feature: X25519Kyber768 key encapsulation for TLS: Not really sure if/how we'd record this one. More of an infrastructure security thing than a web dev feature?
|
Thanks again for your detailed look, @chrisdavidmills! Sounds like everything this PR is proposing is correct then and there are few things that could be added as manual additions to BCD as follow-ups. If you're happy with this PR, then I think you could approve and merge :) |
Yup, agreed. I will do so ;-) |
3 tasks
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 Open Web Docs BCD collector v10.7.1 found new features shipping in Chrome 122 beta which was released yesterday. Currently, the collector covers about 82% 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 44 features as shipping in Chrome 122:
I think all of this is in line with what https://chromestatus.com says currently.
Again, I hope this auto-generated PR is useful to update BCD for the new Chrome 122 more easily and faster. If you have feedback, let me know! /cc @chrisdavidmills