-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Chromium doesn't support ProgressEvent
in Web Workers
#24620
Conversation
ProgressEvent
indicating it is not exposed to Service Worker in chromiumProgressEvent
in Web Workers
researches chromiumthe interface is exposed to Dedicated Worker and Shared Worker in commit, code review, issue, see also whatwg/xhr#19 for related discussion the issue says 38, but per https://storage.googleapis.com/chromium-find-releases-static/cc0.html#cc05eb7361375e97fee38c5fa80d731a46e2ff8f points to be 47, so 47 should instead be used? webkitexposed to worker in commit, issue, changeset firefoxexpose to worker in commit, issue and rev not confirmed: early version of edge: use the latest confirmed version as ie: not required (note deno: how to test? but I guess it is the same version as interface itself (it as a higher version than |
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Summary
the
ProgressEvent
is not exposed to service worker in chromium, which should be as the spec defines , and firefox has implement it yetsee browser issue for status, and it seems to have not progree recently and may not be fixed soon; also see chromium source code
Note: I'm not sure if partial_implementation or impl_url key should be added or not
this can be test using https://worker-playground.glitch.me/
for chrome latest version:
for firefox latest version:
Test results and supporting details
Related issues