Some console functionality is not supported in workers, e.g. addInspectedNode has no sense for worker since there is no DOM tree. I'd like to split the agent into worker and page specific descendants.
Created attachment 116351 [details]
Committed r101081: <http://trac.webkit.org/changeset/101081>
What is the bigger picture here? Do workers get their own Inspector?
(In reply to comment #3)
> What is the bigger picture here? Do workers get their own Inspector?
Worker inspection meta bug describes this in details: https://bugs.webkit.org/show_bug.cgi?id=58541
At the moment we can list all dedicated workers in the Page's inspector and open separate inspector for each of them. It requires window.open to work inside inspector front-end on the platform. In WebKit2 it is blocked by https://bugs.webkit.org/show_bug.cgi?id=72506.
Shared worker also can be inspected using its own web inspector. The idea is to have some discovery page for shared workers which would allow opening inspector front-end for each shared worker. In Chromium we use browser task manager for discovering shared worker processes and inspecting them.