[w3c/IndexedDB] Clarify post abort state of newly created DB in 5.8 (physical persistence vs observable state) (Issue #491)

Taym95 created an issue (w3c/IndexedDB#491)

Part of [Servo IndexedDB implementation](https://github.com/servo/servo/pull/42998) we noticed In [5.8 ("Aborting an upgrade transaction")](https://w3c.github.io/IndexedDB/#abort-an-upgrade-transaction), for a newly created DB, the algorithm says:
- connection.version -> 0
- connection.object store set -> empty set

What is unclear is whether user must:
1) delete the physical backing store, or
2) keep it but make it logically non existent / not visible to web eexposed APIs.

observed behavior (needs confirmation):
- Firefox: physical SQLite file appears to remain.
- Safari: physical DB appears to remain in tooling.
- Chrome: DB may not appear in DevTools after abort.

Questions:
- Is physical on disk deletion intentionally non normative?
- What is the required behavior for `indexedDB.databases()` after aborting the initial upgrade?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/491
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/491@github.com>