712829 - Indexeddb rendering appears broken in latest Windows Nightly

Status: RESOLVED INVALID

(Core :: Storage: IndexedDB, defect)

Description

[John Hammink]

Attachment: content loaded into local indexeddb

Latest Nightly for Windows Desktop FF:
Build identifier: Mozilla/5.0 (Windows NT 6.1; rv:12.0a1) Gecko/20111221 Firefox/12.0a1

To repro: using  http://people.mozilla.com/~jhammink/webapi_test_pages/IndexedDBSingleAdd.html  create a very long list of items, including many with localized non -utf8 chars (see attachment)  

Close the browser, and reopen page.

Expected behavior:  Should see list created in previous step when the page is loaded.

Actual behavior:  Page loaded is blank, with no list. Refreshing browser doesn't reload list.  Adding a new item forces page to refresh old list, with new item added at the bottom of the list.

Comment 1

[John Hammink]

Attachment: disregard prior attachment: content loaded into local db on windows VM

Comment 2

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

This page uses the old setVersion API that was removed in Firefox 10. So it's failing to even open the database.

Comment 3

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Hmm.. actually.. if the database was already created in an earlier version of firefix, the code in that testcase should actually work. Let me look again.

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Oh, yeah, i see the problem.

So of the database already exists, the testcase will successfully open it. However since it's looking for the database to have version "1.98" (???) it will always try to upgrade the database the first thing it does. But that will fail since it tries to do it using the old setVersion API which no longer exists. You should be seeing an error in the error console, are you not?

This is why the list isn't populated on load.

The reason that it works once you add or remove an item is that the testcase uses the already opened database to update all of the displayed information.


The testcase also tries to listen to a non-existing 'onfailure' event which doesn't exist. That doesn't affect anything here though, it just means that error's won't be logged in the developer console.