It's silly, because we totally have ErrorEvent _objects_ in workers (e.g. we fire them for script errors!) but don't expose the ErrorEvent interface. Is there any particular reason to have things this way? Note that at least testing/web-platform/meta/workers/semantics/interface-objects/003.html.ini and testing/web-platform/meta/workers/semantics/interface-objects/001.worker.js.ini will need to be modified if this is fixed.
No reason. Looks like ErrorEvent (webidl) has been that way since it was added in bug 643325
Created attachment 8830555 [details] [diff] [review] expose_interfaces_in_workers.diff We dispatch those events in workers and FileList can be posted to worker. (We have some tests for FileList posting) https://treeherder.mozilla.org/#/jobs?repo=try&revision=257e96d399dca55adefb1b2b92134fcbb153f14c
Oh, I need to add stuff to test_serviceworker_interfaces.html too And mark test passing: TEST-UNEXPECTED-PASS | /FileAPI/idlharness.worker.html
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/47828603cd9c ErrorEvent, CloseEvent, ProgressEvent and FileList should be exposed in workers, r=baku