Safari only partially supports top-level await#26510
Merged
Conversation
Contributor
Author
|
cc @jensimmons |
Elchi3
approved these changes
Apr 29, 2025
Member
Elchi3
left a comment
There was a problem hiding this comment.
We're still working on better guidelines for when to set partial_implementation, but I believe it makes sense here.
This was referenced May 12, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Marks Safari's implementation of top-level await as partial, because it doesn't support
Test results and supporting details
This was reported in #20426 and #26075.
Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=242740
The wording was taken from @shvaikalesh's WebKit PR addressing the issue (not yet merged) .
Related issues
Fixes #20426.