Skip to content
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

Closed
inexorabletash opened this issue May 24, 2016 · 1 comment
Closed

Enforce transaction commit ordering more strictly #77

inexorabletash opened this issue May 24, 2016 · 1 comment

Comments

@inexorabletash
Copy link
Member

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.

@inexorabletash
Copy link
Member Author

I believe this can be addressed in the spec by changing:

When a transaction can no longer become active...

to:

When a transaction has been started and it can no longer become active...

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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant