Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)

pwnall approved this pull request.

The text LGTM, from the perspective of an implementer who's not super-versed in spec subtleties.

> -    lt="start|started">start</dfn> the transaction asynchronously.
-
-1. Once the transaction has been [=transaction/started=] the implementation can
-    start executing the [=requests=] placed against the transaction.
-    Unless otherwise defined, requests must be executed in the order
-    in which they were made against the transaction. Likewise, their
-    results must be returned in the order the requests were placed
-    against a specific transaction. There is no guarantee about the
-    order that results from requests in different transactions are
-    returned. Similarly, the transaction [=transaction/modes=] ensure that two
-    requests placed against different transactions can execute in any
-    order without affecting what resulting data is stored in the
-    database.
+    When a transaction is created its [=transaction/state=] is initially [=transaction/active=].
+
+1. When an implementation is able to enforce the constraints defined for the transaction [=transaction/scope=] and [=transaction/mode=], defined [below](#transaction-scheduling], the implementation must [=queue a task=] to <dfn lt="start|started">start</dfn> the transaction asynchronously.

nit: This line is really long and thus hard to review on GitHub.

-- 
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/pull/242#pullrequestreview-142183757