Re: [w3c/IndexedDB] Integrate with window.onerror (#49)

In the new DOM hook for IndexedDB, `legacyOutputDidListenersThrowFlag` is set after "report the exception" (thus apparently being too late to prevent the default of aborting, consistent with https://github.com/w3c/IndexedDB/issues/140#issuecomment-274399952 ).

> 7. Call a user object’s operation with listener’s callback, "handleEvent", a list of arguments consisting of event, and event’s currentTarget attribute value as the callback this value. If this throws an exception, then:
>
>    1. Report the exception.
>
>    2. Set `legacyOutputDidListenersThrowFlag` if given.

This reporting the exception step itself mentions it needing to ["report the error"](https://html.spec.whatwg.org/multipage/webappapis.html#report-the-error) with the "global object" which would thus appear to trigger `window.onerror` in this later step:

> 7. Let notHandled be the result of firing an event named error at target, using ErrorEvent, with the cancelable attribute initialized to true, the message attribute initialized to message, the filename attribute initialized to urlString, the lineno attribute initialized to line, the colno attribute initialized to col, and the error attribute initialized to errorValue.

So, it looks like this `window.onerror` behavior is already *a fait accompli* given that IndexedDB is also using the `legacyOutputDidListenersThrowFlag` hooks, no? Or is this issue being kept open since tests don't yet exist for it and it is not ready to be officially part of V2 for reasons mentioned above? (I'm mostly just interested in confirming that I am not mistaken that technically this is already spec'd...)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/49#issuecomment-295721032