-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Body Mixin text()
is supposed to return USVString
#39804
Comments
text()
is supposed to return USVString
To be fully compliant, yes we likely need to. |
Should I take this issue up? |
just notice I also wonder what the diffrent is between USVString and a "normal" string is and doing |
Anyone currently working on this issue? If not, can I try to solve it? |
Hi @ronag I am working on this issue. I could see the |
Readable web stream returns strings. Where it supposed to return usvstring. This change will fix the issue Fixes: nodejs#39804 Refs: https://fetch.spec.whatwg.org/#body-mixin
Added test cases for the code changes. Fixes: nodejs#39804 Refs: https://fetch.spec.whatwg.org/#body-mixin
Readable web stream returns strings. Where it supposed to return usvstring. This change will fix the issue Fixes: nodejs#39804 Refs: https://fetch.spec.whatwg.org/#body-mixin
Added test cases for the code changes. Fixes: nodejs#39804 Refs: https://fetch.spec.whatwg.org/#body-mixin
Since the readable web streams already returns USVString The changes made to blob.js and consumers.js are reverted Test cases are added to check surrogate to USVString conversion for ReadablewebStreams Textdecoder and Blob PR-URL: nodejs#40351 Fixes: nodejs#39804
PR-URL: nodejs#40351 Fixes: nodejs#39804
Added test cases to check surrogate code points to usv string conversion in stream consumers and text decoder Fixes: nodejs#39804
Added test cases to check surrogate code points to usv string conversion in stream consumers and text decoder Fixes: nodejs#39804
Added test cases for below scenarios -text() method of stream consumers.js and blob.js should return usv string for incomplete utf-8 byte sequnce. -the textdecoder should return usv string for incomplete utf-8 byte sequnce. Fixes: nodejs#39804
Added test cases for below scenarios -text() method of stream consumers.js and blob.js should return usv string for incomplete utf-8 byte sequnce. -the textdecoder should return usv string for incomplete utf-8 byte sequnce. Fixes: nodejs#39804
Verify that `Blob.prototype.text()`, `streamConsumers.text()` and `TextDecoder.prototype.decode()` work as expected with invalid UTF-8. Fixes: nodejs#39804
Verify that `Blob.prototype.text()`, `streamConsumers.text()` and `TextDecoder.prototype.decode()` work as expected with invalid UTF-8. PR-URL: #40351 Fixes: #39804 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
https://fetch.spec.whatwg.org/#body-mixin
@jasnell I think the
Blob
and consumer helpertext()
methods need to run throughtoUSVString
which is used in theurl
module?The text was updated successfully, but these errors were encountered: