- From: Gregory Terzian <notifications@github.com>
- Date: Sun, 04 Jan 2026 23:26:58 -0800
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 5 January 2026 07:27:02 UTC
gterzian created an issue (w3c/IndexedDB#487) https://w3c.github.io/IndexedDB/#transaction-start > When an implementation is able to enforce the constraints for the transaction’s (...) the implementation must [queue a database task](https://w3c.github.io/IndexedDB/#queue-a-database-task) to start the transaction asynchronously Starting a transaction doesn't seem to require queuing a task, because the state change only affect parallel steps (of https://w3c.github.io/IndexedDB/#async-execute-request). The event-loop will notice when a transaction has started only when the event are fired from within the task queued when an request has been executed. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/487 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/issues/487@github.com>
Received on Monday, 5 January 2026 07:27:02 UTC