- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Nov 2014 00:28:16 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25251 --- Comment #2 from Joshua Bell <jsbell@google.com> --- Just confirming: are we file with still allowing "readonly" transactions to snapshot and thus not block subsequently created "readwrite" transactions with overlapping scope? Spec text is: "There are a number of ways that an implementation ensures this. The implementation can prevent any "readwrite" transaction, whose scope overlaps the scope of the "readonly" transaction, from starting until the "readonly" transaction finishes. Or the implementation can allow the "readonly" transaction to see a snapshot of the contents of the object stores which is taken when the "readonly" transaction started." Chrome implements snapshots, Firefox does not appear to, i.e. in FF a readonly transaction will block a readwrite transaction with overlapping scope. I was thinking of this as the same issue, but I'm okay with a more scoped change as well. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 14 November 2014 00:28:18 UTC