You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one method would bring fetch to full parity with XHR regarding response types, and it'd be very useful for leveraging browsers' streaming parsers when fetching HTML to eventually either parse out (in user scripts) or display (in web pages). It wouldn't stream to the UI itself, however. In spirit, it'd mimic the "set a document response" algorithm for XHRs, and it'd likewise derive the MIME type from the response headers (specifically response.headers.get('content-type')).
The text was updated successfully, but these errors were encountered:
This one method would bring
fetch
to full parity with XHR regarding response types, and it'd be very useful for leveraging browsers' streaming parsers when fetching HTML to eventually either parse out (in user scripts) or display (in web pages). It wouldn't stream to the UI itself, however. In spirit, it'd mimic the "set a document response" algorithm for XHRs, and it'd likewise derive the MIME type from the response headers (specificallyresponse.headers.get('content-type')
).The text was updated successfully, but these errors were encountered: