Since we aggregate WebProcess WebViews under the UIProcess, debuggers were expecting the UIProcess to connect. In some situations it was not connecting so the views never showed up. We should always have the UIProcess connect to webinspectord if it is spawning a WebProcess. <rdar://problem/16676218>
Created attachment 230495 [details] [PATCH] Proposed Fix
Comment on attachment 230495 [details] [PATCH] Proposed Fix Clearing flags on attachment: 230495 Committed r168035: <http://trac.webkit.org/changeset/168035>
All reviewed patches have been landed. Closing bug.
I cannot understand this patch, but is this XPC related? For WinCairo case, there seems no reason to instanciate RemoteInspector object in UIProcess.
(In reply to Basuke Suzuki from comment #4) > I cannot understand this patch, but is this XPC related? For WinCairo case, > there seems no reason to instanciate RemoteInspector object in UIProcess. Yes this is XPC related for Cocoa platforms (encourage the UIProcess to connect to webinspectord when it creates a WebContentProcess that may have a page). This could be made PLATFORM(COCOA) if needed.