Ah yeah, that's a bummer. It's definitely storing the information just fine within scope of the extension, but unfortunately that does nothing if I have no way to retrieve it via the content-script. I'll have to figure another way around it, maybe some crappy workaround that I can find temporarily.
On Aug 21, 2:22 pm, Erik Kay <[email protected]> wrote: > On Fri, Aug 21, 2009 at 12:02 PM, Colin Bleckner<[email protected]> wrote: > > > I haven't tried using this, so I don't know if it's implemented in > > Chrome yet, but there is an event that gets triggered on local storage > > changes:http://dev.w3.org/html5/webstorage/#the-storage-event > > Unfortunately, local storage events aren't implemented > yet:http://code.google.com/p/chromium/issues/detail?id=19972 > > This one may be a little while before it arrives because it's blocked > on DOM Storage locking, which is going to be a fair amount of work. > > Erik > > > > > > > You might be able to use that. > > > Colin > > > Scott Ferguson wrote: > >> So I'm using the localStorage call within scope of the extension to > >> store some information that the user can enter. How would I create an > >> event to fire from a content-script to retrieve this information from > >> the extension? What event would that be? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
