Thanks for all of your inputs. My previous example (gmail addon) might be misleading. Let's say the popular ad block. Ad block should be working on all web sites, and a user should be able to add/edit/delete any specified ad sources. Such information need to be stored locally, and accessible from any web pages by the add-on.
So talking about cookie, IMHO I don't think it is a good candidate for user preferences due to its tight restriction on domains and server interaction. I didn't' follow the latest progress of HTML 5, but I remember it had some security issues due to its widely opened door (especially the globalStorage ). On the other hand a user preference system should be working regardless of a user's security setting. But users might prohibit local storage (especially in the public/topmost domain level) like they do to cookies. I am not an expert in this and my thinking might be wrong. Any of your comments are welcome. In any case looking forward to checking the new Chrome release and trying it out (Real Soon Now, right? :)). Thanks, -Jack On Tue, May 5, 2009 at 4:43 PM, Aaron Boodman <a...@chromium.org> wrote: > On Mon, May 4, 2009 at 11:08 AM, jack <js2...@gmail.com> wrote: >> >> Dear experts, >> >> I am recently playing around Chrome extension development > > Sweet! > >> does chrome have an add-on preference system? I think a >> preference system is an essential component for an add-on ecosystem. >> What I mean is something like Firefox's >> Components.interfaces.nsIPrefBranch: >> >> https://developer.mozilla.org/En/Code_snippets/Preferences >> >> e.g., for a gmail addon, a user should be able to save his/her user/ >> pswd info. WRT to add-on development, how/where to support this? > > Our idea is that in most cases developers will use HTML5 LocalStorage > for this, which will be available to all web pages (including > extensions) by default. > > However, HTML5 LocalStorage is not yet implemented for Chrome, so it > doesn't show up for extensions either. There are people working on > this, though, and we hope to have it available Real Soon Now. > > Note that using cookies, as Peter suggests, won't work either. We have > purposely decided to not enable cookies for extensions since the > concept doesn't really make sense (cookies are really designed for > live web pages that interact with servers). > > - a > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
