- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Apr 2016 09:35:49 +0000
- To: public-media-capture-logs@w3.org
The Service Workers case uses HTML's [report the error](https://html.spec.whatwg.org/multipage/webappapis.html#report-the-error) algorithm to report errors in scripts, so that usage looks like a straightforward extension to what HTML does. > The latter looks ugly, but we get file and line number (and stack) pointing to the `onerror` line, which may be extremely helpful in long promise-chains, whereas in the former case we get nothing. That doesn't sound right. `ErrorEvent` as used in HTML can report the place where a parse error happens. In some ad-hoc testing I wasn't able to see any runtime errors reported using `ErrorEvent`. Having it report where the error event handler was registered (or something like that) sounds strange, are you sure that can be done? The situation you have here looks quite a look like error events on media elements, which use a simple error event and a `MediaError` object. I think that here too, the error can happen at any time and isn't connected to any specific API call where a promise could be rejected? -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/335#issuecomment-208253778 using your GitHub account
Received on Monday, 11 April 2016 09:35:51 UTC