Not blocking the first beta.
blocking2.0: beta1+ → beta2+
This shouldn't block beta 2 either since we haven't even started working on it. Block the final perhaps?
blocking2.0: beta2+ → ?
(In reply to comment #2) > This shouldn't block beta 2 either since we haven't even started working on it. > Block the final perhaps? er..to be clearer, I mean that we haven't started on the sync version of this API at all. The async version is just about ready to land, and that bug is blocking b1.
Nice, early async landed - what's left?
(In reply to comment #4) > Nice, early async landed - what's left? Everything on worker threads, plus recent spec changes (and changes to come).
Final for now, might want to pull it back in to be more aggressive. We can likely do that on some of the other bugs, though.
blocking2.0: ? → final+
So the sync (worker) API will only land in the November final release? It's been very hard to find the answer to this question on the web, on MDC there is more documentation on the sync API than there is on the async one, which makes it even more confusing...
Right now the async api is the one that's in the tree. I think there's work underway on the sync api as well, but we'll know more over the next few weeks/months.
Target Milestone: mozilla1.9.3 → mozilla2.0
While I'm still helping on IndexedDB, I'm not working on it full time anymore. Reassigning to bent to better reflect reality.
Assignee: sdwilsh → bent.mozilla
9 years ago
Depends on: 573176
In FF4b7 createObjectStore no longer works. It fails with the following error: uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIIDBDatabase.createObjectStore]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: http://localhost/test.js :: anonymous :: line 83" data: no] This code has been working since FF4b4 I believe. Sample Code: db.createObjectStore('TestTable', 'ID'); // Where db is the event.result of the // window.moz_indexedDB.open('dbname', 'dbname') // command Guido Tapia
Not blocking on the tracker bug.
blocking2.0: final+ → -
I think we can call this done.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
We don't support sync Indexed DB yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Chrome is allowing access to the async api from web workers. Is there any chance of getting that functionality in Firefox as well? Might be easier to just open the async api up to web workers compared to creating a new sync API. http://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary&groupby=&sort=&id=64054
Adding the sync API and adding the async API are roughly equally difficult at the moment, because adding anything to workers is quite difficult. It's on our radar though, and once the worker DOM bindings are sorted out IndexedDB is one of the first things on the list.
I don't think there's a point to keeping this bug open just because we don't support IDB in workers (sync or async alike). We have separate bugs for those efforts, having a separate tracking bug doesn't buy us anything. If anything we should have a IndexedDB bugzilla component. I'll see what it takes to get that going.
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago → 7 years ago
Resolution: --- → FIXED
(In reply to Jonas Sicking (:sicking) from comment #16) > I don't think there's a point to keeping this bug open just because we don't > support IDB in workers (sync or async alike). We have separate bugs for > those efforts, having a separate tracking bug doesn't buy us anything. Same for documentation. There is https://developer.mozilla.org/en/IndexedDB and sub pages now. We can add dev-doc-needed to separate bugs then as well.
Keywords: dev-doc-needed → dev-doc-complete
IndexedDB does not work on version 21 of firefox. Not just for "workers" The demos ON YOUR OWN SITE do not work. They either tell me that I need a newer version of firefox or that firefox does not support well ... anything. They tell me to see: https://developer.mozilla.org/en/IndexedDB/IDBFactory#Browser_compatibility Also, THERE IS NO INDEXEDDB DEMO, ON ANY SITE, THAT WORKS WITH MY BROWSER. I cannot update anything. What happened to IndexedDB. I even followed the w3 code example. An explanation would be nice.
Brunus, I just updated to Firefox 21 and my test site that uses IndexedDB is still working fine. Give it a try, and if you are still having issues you may want uninstall/reinstall your browser: http://www.shawngoertzen.com/wp-content/Html5Site/ (In reply to Brunus from comment #18) > IndexedDB does not work on version 21 of firefox. > > Not just for "workers" > > The demos ON YOUR OWN SITE do not work. > They either tell me that I need a newer version of firefox or that firefox > does not support well ... anything. > > They tell me to see: > https://developer.mozilla.org/en/IndexedDB/IDBFactory#Browser_compatibility > > Also, THERE IS NO INDEXEDDB DEMO, ON ANY SITE, THAT WORKS WITH MY BROWSER. > I cannot update anything. > What happened to IndexedDB. I even followed the w3 code example. > An explanation would be nice.
Thank you for taking the time to reply. No. The example that you set up does not work in my browser. And ... No. My browser does not need to be "reinstalled". I would love to say that the reason it is not working is that I am limited in my ability as a programmer but this is simply not true. NOT ONE EXAMPLE OF IndexedDB HAS WORKED IN MY FIREFOX BROWSER SO FAR. I do not expect you to reply.
You need to log in before you can comment on or make changes to this bug.