With regard to moving the DOM inspector out of process Sergey Ryazanov have filed https://bugs.webkit.org/show_bug.cgi?id=23502 with a rather large patch where the inspector access to the DOM is being factored to an interface layer which will allow us to move the DOM inspector out-of-process. /Søren
On Tue, Jan 27, 2009 at 7:05 PM, Yury Semikhatsky <[email protected]>wrote: > > > On Tue, Jan 27, 2009 at 8:08 PM, Aaron Boodman <[email protected]> wrote: > >> It seemed complicated to allow other processes direct access to the >> DOM, so we were not going to do that. > > But many extensions will need to access the DOM one way or another. > Are you going to restrict this access or probably inject extensions > code directly into the page(as it's described in early design document)? > > >> 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? > > The main goal for moving Web Inspector into separate renderer process is to > reduce impact of the inspector code on the inspected page. In particular > as > inspector UI implemented in JS it may interfere with the page execution. > So > the question was exactly about that client/server model for inspector/page > communication. > > > > > >> >> >> - a >> >> On Tue, Jan 27, 2009 at 6:35 AM, Yury Semikhatsky <[email protected]> >> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
