Chrome 130 supports WebAssemblyCompileOptions, which enable JS String Builtins #25391
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:wasm
caugner
requested changes
Dec 13, 2024
There was a problem hiding this comment.
LGTM overall, just the spec_url doesn't seem specific enough.
PS: It is what we currently do, but I really don't like this data duplication (6 feature for what is likely covered by the same implementation) and would prefer a way to inherit support data from another feature.
Elchi3
reviewed
Dec 13, 2024
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
Co-authored-by: Florian Scholz <[email protected]>
caugner
changed the title
Merged
ddbeck
added a commit
to ddbeck/browser-compat-data
that referenced
this pull request
Jan 18, 2025
Reading across the following links, it appears that Firefox implemented the same thing as Chrome, but when Chris added the `compile_options` keys they weren't reconciled with the existing Firefox data. - https://bugzilla.mozilla.org/show_bug.cgi?id=1863794 - mdn#25230 - mdn#25391 Discovered in the course of web-platform-dx/web-features#2549
Elchi3
pushed a commit
that referenced
this pull request
Jan 20, 2025
…5706) Show Firefox support across all of wasm JS string built-ins Reading across the following links, it appears that Firefox implemented the same thing as Chrome, but when Chris added the `compile_options` keys they weren't reconciled with the existing Firefox data. - https://bugzilla.mozilla.org/show_bug.cgi?id=1863794 - #25230 - #25391 Discovered in the course of web-platform-dx/web-features#2549
ddbeck
added a commit
to ddbeck/browser-compat-data
that referenced
this pull request
Jan 27, 2025
ddbeck
added a commit
to ddbeck/browser-compat-data
that referenced
this pull request
Jan 27, 2025
Elchi3
pushed a commit
that referenced
this pull request
Jan 27, 2025
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.
Summary
Chrome 130 supports WebAssembly JS String builtins. Specifically, This PR adds data points for the
compileOptionsparameter used to enable these built-ins, which is added to:WebAssembly.compile()WebAssembly.compileStreaming()WebAssembly.instantiate()WebAssembly.instantiateStreaming()WebAssembly.validate()WebAssembly.Module()constructorTest results and supporting details
See https://chromestatus.com/feature/6695587390423040 for the data source. I have also tested each of the above cases and found them to work by default in Chrome 130/131.
Related issues