Tuesday, June 6th, 2006
Firefox 2: Client-side storage and a lot more
Category: Firefox
Firefox Bon Echo Alpha 3 just came out into the wild. This gives us a glimpse into new features that we will be getting.
The big item is Client-side session and persistent storage meaning that we will be able to use JavaScript to:
JAVASCRIPT:
-
-
sessionStorage.setItem(..)
-
-
and
-
-
globalStorage.namedItem(domain).setItem(..)
-
There are also other nice features such as microsummary support, anti-phishing, and inline spellchecking.
3.9 rating from 38 votes
That’s great. Now we have another feature that we can only use in one brand of browser.
Nice! How is this different than from Dojo storage aside from using a different provider (I believe right now Dojo uses Flash to store content).
@Oliver
This isn’t different from dojo.storage: this is just a simpler architecture that it could implement in preference to the labyrinth of dojo.flash communications.
You can try it http://channy.creation.net/work/firefox/domstorage/ and http://people.mozilla.org/~myk/microsummaries/generators/
[…] Firefox 2: Client-side storage and a lot more […]
Hi folks; dojo.storage uses the concept of StorageProviders to encapsulate the specific way in which storage is done, giving a unified API for storage over different platforms, browsers, and environments. I plan on creating a WhatWGStorageProvider (which is the spec on which the Firefox storage is based on) which will use the native browser storage if it is available. Your code that uses dojo.storage would then not have to change when the new browser comes out - you can start using storage today (which uses Flash under the covers).
I’d love if someone submitted a WhatWGStorageProvider to me (which means it will happen faster); an IEStorageProvider would be nice too (the one that uses IE’s proprietary 60K of client side storage - see http://codinginparadise.org/weblog/2005/08/ajax-internet-explorer-has-native.html for details)
Yes, dojo.storage is still needed to abstract the browser differences…
How many iterations will it take for browsers to get to a standard client-side storage solution?
One more thing that is frustrating with these APIs: each browser uses a different store. This was an un-forseen advantage of using Flash for storage: it shares the same data store between browsers…
sound good, but no body can develope a *firefox only* application in the market.
sounds good, but no body dare to develop a *firefox only* application in the market.
[…] Ajax, AjaxPatterns, Dojo, Firefox, Flash, LocalStorage, Storage Local storage - beyond 2KB cookies - is now a step closer with the latest Firefox effort. You get a local storage API like this: sessionStorage.setItem(..) and globalStorage.namedItem(domain).setItem(..) […]
Obviously this has potential for security problems:
“globalStorage['’] is accessible to all domains.”
I’d like to know how they plan on stopping people abusing it.
I agree with that:
“sounds good, but no body dare to develop a *firefox only* application in the market.”
[…] Firefox 2: Client-side storage and a lot more: “Firefox Bon Echo Alpha 3 just came out into the wild. This gives us a glimpse into new features that we will be getting. […]
hope ie will support this features
chenng, this is unfortunately true for now, but this storage system is not a proprietary feature. Hopefully other browsers (Opera and Safari comes to mind) will add support to it soon, and someday we may see IE offering it too. For now, I guess the best way is to use an abstract system like dojo.storage, that takes advantage of whatever your browser supports.
About the security problem, I thought of that too, but while taking a quick look at the docs it seems like though the global-domain storage in theory does exist, websites can’t access it at all, because of the inherent security model of the specifications. I have to read it more carefully to confirm that.
Any effort to remove the inherent symptoms of Alzheimers in browsers surely helps. Dojo.storage use of Flash, regardless of how many tears they shed peeling the onion, is sweet and removes browser idio(t)syncrasies.
[…] Firefox 2: Client-side storage and a lot more […]
It seems to me that sessionStorage is a W3c spec that will appear officially soon: see http://www.whatwg.org/specs/web-apps/current-work/
IE already does support something very much like this feature and has for many years:
http://msdn.microsoft.com/library/default.asp?url=/workshop/author/persistence/overview.asp
This means that to do simple local storage in the two major browsers will no longer require the overhead of a flash object.
Help me please…
I just installed Firefox 2.0, and all of a sudden, my username/password isn't being inserted in the signon window (it always was before). I tried the usual suspects–I did not mistakenly tell FF not to remember the password for this site; and I also tried the remember password bookmarklet, but all to no avail–FF will not ask me to remember this password. What do I need to do to get around this?
Please add firefox cookies/bad web sites immunization in next version!
Firefox 2 cannot reject third party cookies!!!!!!!!
I stick with firefox. I tried upgrading to IE7 but then the FTP drag and drop would not function.
Ive tried this but some of my normal function dont seem to be working either. Is this because they’re obsolete now?