Add "text" destination type, for JavaScript text imports #794
Conversation
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
Member
Author
|
I've now linked my W3C account with my GitHub account, could the ipr check be revalidated? |
This was referenced Dec 17, 2025
Member
|
Thanks for the patch and for pointing to the tests. They both look reasonable to me, assuming the HTML and Fetch patches are accepted. Once those land, landing this should be straightforward. :) |
mikewest
approved these changes
Dec 17, 2025
ctcpip
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This change is to support the changes in whatwg/html#11933 and whatwg/fetch#1898, by adding
textas a destination type.Tests for this are included in web-platform-tests/wpt#56812.
Preview | Diff