-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] data urls are not handled properly #18
Comments
isaacs
added a commit
that referenced
this issue
Nov 8, 2021
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
isaacs
added a commit
that referenced
this issue
Nov 8, 2021
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
isaacs
added a commit
that referenced
this issue
Nov 8, 2021
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
isaacs
added a commit
that referenced
this issue
Nov 9, 2021
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
wraithgar
pushed a commit
that referenced
this issue
Mar 1, 2022
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
wraithgar
pushed a commit
that referenced
this issue
Mar 1, 2022
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
wraithgar
pushed a commit
that referenced
this issue
Mar 1, 2022
1. No longer requires `;base64` to be included on `data:` URIs. 2. Supports immediately aborting `data:` URIs. Fix: #18
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
What / Why
data:
urls should be supported the "same" as fetched URLs, in the sense that they may be aborted, and should support any validdata:
urls, whether base64 encoded or not.Expect it to fail with an AbortError. Instead it works. (This mirrors
node-fetch
, but diverges from browser fetch.)Expect: load all data urls. Actual: fails because they are not base64 encoded.
Again, mirrors node-fetch, but not browser fetch.
The text was updated successfully, but these errors were encountered: