[w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237)

It has been suggested that commit() is a good fit for IDB transactions in "end-of-life" eg. when the page is freezing (per [Web Lifecycle](https://github.com/WICG/web-lifecycle)) or unloading (user navigates away).
In these cases oncomplete and onabort will not fire. If the transaction fails it would be useful to surface this to the app, on next IDB access. How should such failures be surfaced to the app (in onresume or new load)?

@inexorabletash 
@philipwalton



-- 
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/237