Bug 1523562 [wpt PR 14761] - [IndexedDB]: Explicit commit error timing handling., a=testonly

Automatic update from web-platform-tests
[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: w3c/IndexedDB#242

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

--

wpt-commits: b0fbbb9ff451b18bf8a69fd54027bf59d21c2667
wpt-pr: 14761

UltraBlame original commit: a87a214e284e09b1a0b92c67da0c216fb669b979

Author: marco-c