Thanks. That's cool. Though a slick shared DB/storage solution via Bug 30224 would be way cooler.
On Jan 20, 6:12 pm, hexid <nick.curr...@gmail.com> wrote: > Yes, for the time being you need to use message passing to get the > data from the options page... > > You can star this bughttp://code.google.com/p/chromium/issues/detail?id=30224 > to get notices on the status of direct variable and localstorage usage > between background/options/popup pages and the content scripts... > > On Jan 20, 6:30 pm, Colin Bleckner <co...@xmarks.com> wrote: > > > > > As far as I know you can't directly access your extension's SQL database > > directly from a content script. Instead you'll need to use some sort of > > message passing to ask your extension for the setting information you > > need:http://code.google.com/chrome/extensions/messaging.html > > > Colin > > > On 1/20/2010 17:26, GeorgesMouth wrote: > > > > I tried experimenting with a fancy new HTML5 client SQL database for > > > my options page. It's really cool. But, I'm not quite seeing how to > > > best retrieve my user options from the DB. > > > > Anyone know if it's possible to give my content script access to the > > > option page's DB? -- 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.
