-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal : response.html() #15
Comments
Same as #16, and this one is addressed directly in the document. |
yutakahirano
added a commit
that referenced
this issue
Jun 23, 2020
# This is the 1st commit message: # This is a combination of 23 commits. # This is the 1st commit message: Integrate CORP and COEP This is part of the introduction of COEP (whatwg/html#5454). The CORP check now takes COEP into account. Also, responses coming from service workers are checked. # This is the commit message #2: Update fetch.bs Co-authored-by: Domenic Denicola <[email protected]> # This is the commit message #3: Update fetch.bs Co-authored-by: Domenic Denicola <[email protected]> # This is the commit message #4: fix # This is the commit message #5: fix # This is the commit message #6: fix # This is the commit message #7: fix # This is the commit message #8: fix # This is the commit message #9: fix # This is the commit message #10: fix # This is the commit message #11: fix # This is the commit message #12: fix # This is the commit message #13: fix # This is the commit message #14: fix # This is the commit message #15: fix # This is the commit message #16: fix # This is the commit message #17: fix # This is the commit message #18: Update fetch.bs Co-authored-by: Anne van Kesteren <[email protected]> # This is the commit message #19: Update fetch.bs Co-authored-by: Anne van Kesteren <[email protected]> # This is the commit message #20: fix # This is the commit message #21: fix # This is the commit message #22: fix # This is the commit message #23: fix # This is the commit message #2: fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
window.fetch
is a great progress to make asynchronous requests, thanks for that!I am not sure whether that's the right place for doing so, I also propose that we can parse the response as HTML content.
Something like
response.html([context])
wherecontext
is the parent node of where the nodes would be inserted. It would returnPromise<DocumentFragment>
.A polyfill of them would be:
Use case: having directly parsed elements to possibly manipulate their content before inserting.
What do you think?
Florent
The text was updated successfully, but these errors were encountered: