-
Notifications
You must be signed in to change notification settings - Fork 71
Description
From working on the Ladybird implementation of this spec, I've encountered some parts that could use clarification..
-
Opening a database connection step 10.8 says
If the upgrade transaction was aborted, but there is no mention elsewhere in the steps where theupgrade transactioncomes from. (Also not how to check if its aborted.. See next bullet) -
The only way to tell if a transaction was aborted seems to be if the transaction has an error, but when calling IDBTransaction::abort(), the error is set to null (It calls abort a transaction with a null parameter).
So this abort is not marking the transaction as aborted? -
In abort a transaction, step 6.3.1, it says to use
the open request associated with transaction, but there is no spec steps that sets this anywhere -
In delete a database, step 5. wants
the set of all connections associated with db, but there are no steps to create this association -
In IDBFactory::open, step 4 creates a new
open request, and then dispatches an event to this during step 5.2.3. Then later it is returned as aIDBOpenDBRequest. Is theopen requesta IDBRequest? And if so, is there a reason to not create an IDBOpenRequest directly in step 4?