-
Notifications
You must be signed in to change notification settings - Fork 133
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
Expose ProgressEvent to ServiceWorker #305
Comments
I guess it's too late to stop doing that? |
"that" being exposing FileReader to service workers? Now all major browsers have implemented Blob.stream/text/arrayBuffer there at least is an alternative to FileReader (other than wrapping a Blob in a Response). My gut feeling is that actually removing FileReader from service workers would be challenging though. |
Yeah, removing |
Hey!! |
Lines 1764 to 1765 in b7726ee
Currently the line 1764 lacks |
Hey!! I wanna do that will you please assigned this issue to me that will be great . |
I don't think assigning is used in this repo. Just open a PR and make sure you include |
Thank You |
Hmm, I mean when you open a pull request after writing the actual fix, you'll want to include the "Fixes" text to the content body of the post. It's not a requirement but just a recommendation, so if you have no idea please just proceed. |
Understood...But no Description box is coming. |
You committed the fix and you see that message? Weird, could you share the screenshot? |
Can we please start it again? |
No problem! The easiest way:
I'll happily write steps for GitHub Desktop if you are using it BTW. |
@saschanaz |
FileReader is exposed to ServiceWorker and uses ProgressEvent, but the event interface is not exposed to ServiceWorker since 9d0a9bb.
Exposing it to ServiceWorker also matches Gecko and WebKit implementation:
The text was updated successfully, but these errors were encountered: