Yes, it used to mean. Now it is enabled by default for extensions only and the explicit flag enables it for the rest of the domains. This is not really a web coding support group. You can check out samples from former threads that discussed LocalStorage, or go to the HTML 5 Specifications Document draft for reference.
☆PhistucK On Fri, Sep 18, 2009 at 17:32, Ariën Holthuizen <[email protected]> wrote: > Hmm, I believe that --enable-extensions used to imply > --enable-local-storage, not sure what it's like now that extensions are > enabled by default. Doesn't take away the fact I need to know how to use it, > extension domain or not. [?] > > > On Fri, Sep 18, 2009 at 16:28, PhistucK <[email protected]> wrote: > >> In order to use it on non extension domains, you have to use >> --enable-local-storage, as far as I know. >> ☆PhistucK >> >> >> On Fri, Sep 18, 2009 at 15:51, arienh4 <[email protected]> wrote: >> >>> >>> I'm trying to use localStorage to store preferences and such for a >>> content script. I'd like to take advantage of the fact that >>> localStorage is domain-specific by storing per-domain settings. Could >>> someone give me some pointers on the code? Any attempt I tried hasn't >>> worked. I'd also like to learn about using a background-page to store >>> extension-wide data. >>> >>> >>> >> > > > -- > Ariën > arienh4.net > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
<<inline: 330.gif>>
