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

inexorabletash commented on this pull request.



> -    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.

Tab has been advocating for line breaking at logical (sentence, clause) boundaries rather than to just wrap at 80 columns and reflowing, since that makes future diffs easier to parse. That said, there are some places this could break.

-- 
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#discussion_r217456393