Hmm... interesting problem. This is the first example I'm seen that really shows the need to be able to access extension local storage from content scripts -- that it goes beyond an issue of convenience. Are you using run_at: document_start for your content script? That will improve latency to some extent.
It is also possible (though not easy) to get access to a web page's local storage. You're right that this is a bit of a hack, and spreads your state out over multiple places. I would just treat the page's local storage as a cache, and name it with some key that is unlikely to collide (__myextension__...). The normal way of just calling window.localStorage will not work, because we've not implemented the connection from local storage to content scripts yet. But you can work around that with: http://code.google.com/chrome/extensions/content_scripts.html#host-page-communication - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
