-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce transaction commit ordering more strictly #77
Labels
Comments
I believe this can be addressed in the spec by changing:
to:
|
inexorabletash
added a commit
to web-platform-tests/wpt
that referenced
this issue
Jun 21, 2016
Tracked by w3c/IndexedDB#77 Ensure that a transaction with no requests filed against it still completes in the same order as a transaction with requests (i.e. after previous readwrite transactions with overlapping scope).
ivanzr
pushed a commit
to ivanzr/web-platform-tests
that referenced
this issue
Jun 29, 2016
…orm-tests#3154) Tracked by w3c/IndexedDB#77 Ensure that a transaction with no requests filed against it still completes in the same order as a transaction with requests (i.e. after previous readwrite transactions with overlapping scope).
ddorwin
pushed a commit
to ddorwin/web-platform-tests
that referenced
this issue
Sep 13, 2016
…orm-tests#3154) Tracked by w3c/IndexedDB#77 Ensure that a transaction with no requests filed against it still completes in the same order as a transaction with requests (i.e. after previous readwrite transactions with overlapping scope).
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://github.com/dmurph/indexed-db-observers/issues/24
Even though operation order is well defined by the spec, when a commit occurs for an empty transaction may be underspecified.
The text was updated successfully, but these errors were encountered: