Joshua Bell

Win7 I should note that the network share is not remote per se: it's provided by the physical machine hosting the VM. Still, there could be a timing issue, or...

Just to make sure we're on the same page, the case which failed for me was "read from HDV file on a share and write to physical CF card", using...

Per offline conversations with @domenic it seems like we should try making requests thennables. I don't think we can change the methods to not throw; much existing code relies on...

Presumably the IDL would look like: ``` webidl interface IDBThennableThing { ... Promise then(any onFulfilled, optional any onRejected); Promise catch(any onRejected); ... }; ``` I also assume this is rare...

Noted one possible issue with this: https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/storage/indexeddb/resources/promise-idb.js?l=15 This is an existing bit of code that returns a transaction via a Promise: ```js const transact = (db, scope, mode) => Promise.resolve(db.transaction(scope,...

We need to precisely specify promise resolution & microtask execution vs. event dispatch. Are events dispatched _before_ the request's promise is fulfilled or _after_? If _after_, it's too late by...

Hallway conversations with @littledan - no solutions, still gathering thoughts. To clarify the problem a bit more, if transactions were not automatically aborted here's how you could write it: ```...

In email to public-webapps, @domenic suggests returning tx.complete as a convenience.

As hinted at in #9 it may be convenient to make it a pass-through so you can write e.g. ``` js const url = await tx.objectStore('urls').get(key); const request = await...

Another data point in favor of behavior 1: ``` js async function doStuff(db, url) { const tx = db.transaction('store', 'readwrite'); const store = tx.objectStore('store'); let record = await store.get(url); if...