We only expose the extension bindings for pages with URLs of the form "chrome-extension://*". See chrome/renderer/render_thread.cc and search for RegisterExtension. The (unfortunately named) v8 extension mechanism is how the bindings get added.
On Fri, Oct 23, 2009 at 2:13 PM, Patrick Horn <[email protected]> wrote: > > Hi, > I am writing a new browser (source at > http://github.com/danielrh/berkelium/ ) using the RenderViewHost layer > of chrome. > > I want to be able to send messages to the host process, and it looks > like the chrome.extensions.sendMessage() API is perfect for this. > However, when I do "host()->AllowBindings(BindingsPolicy::EXTENSION)" > (before CreateRenderView, where it is used), no extension object is > added to window.chrome. > > I have also tried with AllowBindings(BindingsPolicy::EXTERNAL_HOST) > which would provide an alternative message passing API. However, adding > this flag just created an empty javascript object at window.externalHost. > > Any thoughts? > > Thanks, > Patrick > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
