[w3c/IndexedDB] How a transaction is implemented as a queue hang (#291)

Generally speaking, the above requirements mean that any transaction which has an overlapping scope with a read/write transaction and which was created after that read/write transaction, can’t run in parallel with that read/write transaction.（Mentioned in [W3C](https://w3c.github.io/IndexedDB/#transaction-scheduling)）

And my question is :
How does indexedDB do to suspend the remaining transactions when multiple read/write transactions are opened at the same time? Is it done with the browser's Event Loop?

-- 
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/issues/291