[XHR] XSLTProcessor #30163
Merged
[XHR] XSLTProcessor #30163
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
|
Preview URLs |
teoli2003
approved these changes
Nov 9, 2023
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.
Part of #30131.
Use fetch()+DOMParser instead of synchronous XHR to fetch XSL and XML documents.
The bit about "For the actual transformation,
XSLTProcessorrequires an XML document..." seemed to be attached to the wrong section, so I moved it.I have tested the first example and it works great! The second example I could not get to work in its original form, but I have checked that the fetch part works, so I don't think it is any more broken than before.