It is by design, for now at least. The content script has only access to the Message Passing API and that is it, in terms of extension APIs.
You can send a message from the popup to the current tab with the needed information and set up a message receiving event in the content script. ☆PhistucK On Tue, Dec 22, 2009 at 12:18, pdknsk <[email protected]> wrote: > I noticed that contents scripts don't share localStorage, is that > intended or a bug? They can access localStorage, but apparently a > separate copy of it. What would be the best way to get a variable set > in popup.html to a content script then? > > -- > > 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]<chromium-extensions%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- 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.
