Hi folks,
Please see dev-platform post:
https://groups.google.com/d/msg/mozilla.dev.platform/3IqDew1O-Vk/-6RQcskrnOgJ
-bent
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Hi folks,
Bug 701634 has landed and IndexedDB is now available in DedicatedWorker,
SharedWorker, and ServiceWorker. Please file any bugs you find in Core :: DOM :
IndexedDB.
-bent
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozill
Thanks for your post!!
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Hi folks,
Just a heads-up that bug 994190 has landed on mozilla-inbound and will soon be
making its way to mozilla-central.
The actual IndexedDB API hasn't changed, and all the tests are green, so
everything should just continue to work. The big win here is that we no longer
have to bounce eve
Hi folks!
https://twitter.com/grssam/status/506675405718171648
Apparently you go to the DevTools toolbar, click the "Settings" button, then
enable the checkbox for "Storage". Then you can browse to a page with IDB and
see what's stored.
I didn't write this and it hasn't been fully publicized y
On Fri, May 23, 2014 at 8:22 AM, Gareth Aye
wrote:
> Thanks! Shall I mark 994190 blocking 701634?
Yes.
- Kyle
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Thanks! Shall I mark 994190 blocking 701634?
On Fri, May 23, 2014 at 11:20 AM, Kyle Huey wrote:
> Most of the work is happening in bug 994190.
>
> - Kyle
>
> On Fri, May 23, 2014 at 8:02 AM, Gareth Aye
> wrote:
> > Hey B2G,
> >
> > I've heard from a couple people that work is underway to enabl
Most of the work is happening in bug 994190.
- Kyle
On Fri, May 23, 2014 at 8:02 AM, Gareth Aye
wrote:
> Hey B2G,
>
> I've heard from a couple people that work is underway to enable accessing
> the indexedDB apis from web workers, but the info on the bug
> (https://bugzil.la/701634) is quite opa
Hey B2G,
I've heard from a couple people that work is underway to enable accessing
the indexedDB apis from web workers, but the info on the bug (
https://bugzil.la/701634) is quite opaque. Is this something that's being
worked on? Do we perhaps need more evidence / use cases?
If someone is workin
Hey,
We recently landed a big change in the DB upgrade process for the
mozContacts API. I thought it could interest some of you, so here are
the relevant links with the patches:
[1] Bug 951806: changes the upgrade code
[2] Bug 932803: tests the upgrade code path
# The problem
The problem was
Le 11/01/2014 06:25, Bob Thulfram a écrit :
> I wrote a blog post about IndexedDB.
> http://firefoxosgaming.blogspot.com/2014/01/indexeddb-game-programming.htmland
> an earlier one on async_storage.js at
> http://firefoxosgaming.blogspot.com/2014/01/asynchronous-storage-game-programming.html
>
> Af
I wrote a blog post about IndexedDB.
http://firefoxosgaming.blogspot.com/2014/01/indexeddb-game-programming.htmland
an earlier one on async_storage.js at
http://firefoxosgaming.blogspot.com/2014/01/asynchronous-storage-game-programming.html
After some discussion, it looks like the best storage opt
Le 05/08/2013 00:50, Andrew Sutherland a écrit :
> On 08/04/2013 06:32 PM, Brian Smith wrote:
>> 4. I think we should be working towards a goal of making DeviceStorage
>> permission from the email app, by improving the capabilities of the
>> alternatives that would make the use of DeviceStorage unn
On Sun, Aug 4, 2013 at 7:51 AM, Andrew Sutherland
wrote:
> On 08/04/2013 01:48 AM, Jonas Sicking wrote:
>> I think we might have an implementation bug right now so that when you
>> use XHR to submit a Blob, we load that whole Blob into memory. That is
>> something we should be able to fix though.
On 08/04/2013 06:32 PM, Brian Smith wrote:
4. I think we should be working towards a goal of making DeviceStorage
permission from the email app, by improving the capabilities of the
alternatives that would make the use of DeviceStorage unnecessary.
(I am assuming s/making DeviceStorage permissi
On Fri, Jun 28, 2013 at 4:37 PM, Andrew Sutherland <
asutherl...@asutherland.org> wrote:
> There is the begged question of whether the e-mail app should try and
> avoid creating duplicate copies of blobs when the Blob is actually a File
> from DeviceStorage and we are able to detect this. (Do File
On 08/04/2013 01:48 AM, Jonas Sicking wrote:
Wow, lots of different subjects here. And I don't fully see how they
all tie together. I'll try to answer the parts that I understand, but
let me know if I missed anything.
Thanks for the very thorough follow-up!
OTOH, if you are saving the draft
On Fri, Jun 28, 2013 at 7:37 AM, Andrew Sutherland
wrote:
> Currently, when you save a draft with attachments in the e-mail app, the
> attached files will be duplicated from wherever they came from (probably
> DeviceStorage) into the IndexedDB blob store. It's my understanding that we
> model the
Thank you Bent, this is some we definitively need!
On 15/07/13 18:55, pancake wrote:
Awesome! I was also wondering about this.
Is there any reason why indexeddb are stored inside sqlite instead of using the
filesystem? I see a performance loss on that...
Another random question. Are we using
Awesome! I was also wondering about this.
Is there any reason why indexeddb are stored inside sqlite instead of using the
filesystem? I see a performance loss on that...
Another random question. Are we using latest sqlite code? Ive recently seen
that now it uses mmap and that makes the db acces
Hey folks,
It's been pointed out often enough that we don't have any convenient way to
inspect IndexedDB databases... So I made an extension for it:
https://github.com/benturner/idbbrowser
It's still an early prototype so please feel free to file bugs when you find
them.
Firefox is currentl
This has now moved to AMO:
https://addons.mozilla.org/en-US/firefox/addon/indexeddb-browser/
-bent
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Currently, when you save a draft with attachments in the e-mail app, the
attached files will be duplicated from wherever they came from (probably
DeviceStorage) into the IndexedDB blob store. It's my understanding
that we model the internal storage where IndexedDB lives as very
limited, so thi
23 matches
Mail list logo
