IndexedDB: tracing output should include transaction id for onComplete operation |
|||
Issue descriptionChrome Version: 66.0.3359.181 (Official Build) (64-bit) OS: Linux What steps will reproduce the problem? (1) Open chrome://tracing (2) Select IndexedDB (3) Visit a page that includes IndexedDB API calls, including a transaction that results in onComplete being called What is the expected result? The trace element for onComplete should include the transaction id. What happens instead? The onComplete doesn't list the transaction id.
,
May 24 2018
,
May 24 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/215ddfcaff790963decde5d45a6914e33afe346e commit 215ddfcaff790963decde5d45a6914e33afe346e Author: Chase Phillips <cmp@chromium.org> Date: Thu May 24 21:16:15 2018 IndexedDB: include tx id in tracing output Bug: 846408 Change-Id: Ib2b7fe4adcc948b88a6fbc46f9a2a678ce016aa3 Reviewed-on: https://chromium-review.googlesource.com/1072187 Commit-Queue: Chase Phillips <cmp@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#561630} [modify] https://crrev.com/215ddfcaff790963decde5d45a6914e33afe346e/third_party/blink/renderer/modules/indexeddb/idb_transaction.cc
,
May 25 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by c...@chromium.org
, May 24 2018Status: Assigned (was: Untriaged)