- From: beidson <notifications@github.com>
- Date: Fri, 04 Nov 2016 12:54:10 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Message-ID: <w3c/IndexedDB/issues/109@github.com>
Behavior tested by transaction-abort-multiple-metadata-revert.html is not obviously specified anywhere
That's vague and is a mouthful, so let me explain.
This test creates some object stores, and each objectstore has an index.
At one point in the test, it:
1 - Grabs an object store handle.
2 - Deletes the references object store (which has an index)
3 - Verifies that the object store handle's set of index names is empty:
`
database.deleteObjectStore('not_books');
...
assert_array_equals(
store.indexNames, [],
'IDBObjectStore.indexNames for the deleted store3 should be empty ' +
'immediately after IDBDatabase.deleteObjectStore() returns');
`
The problem is... I can't find where this behavior is actually specified.
Looking at the steps for IDBDatabase.deleteObjectStore, looking at behavior for "object store handle" or "index set" and other related terms... I can find nothing that states that once an object store is deleted that the object store handles referencing it should have their indexNames set cleared out.
Note: I'm not arguing with the behavior. The behavior might make sense. I see that it could go either way but don't feel strongly about it.
I'm just arguing that the behavior is either:
1 - Not specified
2 - Specified, but in a non-obvious way, and that we should make it more obvious.
--
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/109
Received on Friday, 4 November 2016 19:55:07 UTC