commit c3a88aa79d8710f81cc84679f7c7eaa1e6326100
author Andreas Butler <andreasbutler@google.com> Thu Jan 24 19:42:46 2019
committer Commit Bot <commit-bot@chromium.org> Thu Jan 24 19:42:46 2019
tree 51a01301b08b5e2248abfca6a5f269ccfa566cfc
parent 3afd521c2a5e85a64c387ea5c83d55b293e2751f

[IndexedDB]: Explicit commit error timing handling.

When a transaction is explicitly committed, there may yet be unhandled
errors that the browser has sent but the renderer has not yet seen. This
can cause strange behaviour (see the Github discussion link below). This
patch keeps track of the 'handled errors' in the renderer and the 'sent
errors' in the backend. The 'handled errors' number is sent when the
transaction is explicitly committed, and the browser can compare this
with the 'sent errors'. If they don't match, the transaction is aborted

GitHub Discussion: https://github.com/w3c/IndexedDB/pull/242

Bug: 911877
Change-Id: I7ea7b9e20c70528de3f363e961f87a3d8f5798d3
Reviewed-on: https://chromium-review.googlesource.com/c/1378806
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Andreas Butler <andreasbutler@google.com>
Cr-Commit-Position: refs/heads/master@{#625780}