Bug 155045 – indexNames is empty inside 2+ upgradeneeded event transaction

• Component: New Bugs
• Status: RESOLVED WORKSFORME

[Dmitry Sorin]

Created attachment 273039 [details]
bug description

1. First, open database with version 1
2. Create object store there
3. Add some indexes, ensure that objectStore.indexNames contains all indexes
4. Close database
5. Open this database again with version 2

Actual result: objectStore.indexNames is empty inside upgradeneeded event transaction
Expected result: objectStore.indexNames should contain all indexes created on step 3

[Dmitry Sorin]

Btw, this bug cn be reproduced on mobile Safari too

[Brady Eidson]

At this point, testing IndexedDB with Safari 9 (or MobileSafari on iOS 9) is mostly irrelevant.

Does this happen with a WebKit nightly?

[Brady Eidson]

Created attachment 273096 [details]
Clickable test case

Previously attached test case was just some javascript.

This is an HTML file ready to run, both in the browser or in WebKitTestRunner.

This works perfectly fine for me on Safari 9's WebKit and in ToT WebKit.

[Brady Eidson]

Closing as WORKSFORME: Please try the attached HTML test case to see if it works for you.

If not, please try again in a WebKit nightly.

[Dmitry Sorin]

Made a bit of research.

First: this problem is reproduced in "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56" and not reproduced on my local "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4".

Second, createIndex replaces one of the indexes in 2+ versionchange transaction.

[Dmitry Sorin]

Probably it's better to create another bug for it.

[Dmitry Sorin]

UPD: and yes, it's not reproducable in Webkit nightly.