It seemed complicated to allow other processes direct access to the
DOM, so we were not going to do that. For something like the
inspector, what we were thinking is a client/server model, with the
client being JS that interacts with the DOM and the server being in
another process and showing the inspector UI.
What are the goals for moving the inspector out of the renderer process?
- a
On Tue, Jan 27, 2009 at 6:35 AM, Yury Semikhatsky <yu...@chromium.org> wrote:
> Hi,
> I work on Web Inspector/JS Debugger in Chrome. Currently we're trying
> to move it out of the renderer process of the inspected page.
> To be able to run Web Inspector in its own process we need a way to
> access inspected page resources, DOM and v8 instance from outside
> of the page's renderer process. Since extensions are also supposed to
> live in separate processes it seems that we could share the framework
> for resource access with them or even better implement Web Inspector
> as a regular extension. I wonder what the current state of the extension
> framework is and if there are still plans to give extensions access to the
> inspected page that we can reuse in Web Inspector?
> Thanks,
> Yury
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
