- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Apr 2017 23:06:44 +0000
- To: public-houdini-archive@w3.org
I guess yeah, if you have no ability to e.g. send the error somewhere with fetch(), then having a self.onerror handler isn't super-useful. It still feels wrong to just drop the error into developer tools and never let web devs see it... but I'm not sure what the alternative is. In this case probably what we need is for HTML's "report an exception" to stop assuming the global is always an EventTarget. In the meantime you should probably add a monkeypatch note to worklets saying something like > When asked to [report an exception], do nothing instead, as HTML's [report an exception] needs updating to work with non-EventTarget global objects. That is tracked in whatwg/html#XYZ. -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/396#issuecomment-298126269 using your GitHub account
Received on Friday, 28 April 2017 23:06:51 UTC