[Webkit-unassigned] [Bug 51364] Web Inspector: Remote Web Inspector for platform/mac

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jan 18 10:30:41 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=51364





--- Comment #20 from Joseph Pecoraro <joepeck at webkit.org>  2011-01-18 10:30:40 PST ---
I will put part 5 up later today that allows WebViews to opt-out of being
listed for remote inspector. However, the following situation can occur,
which is difficult to handle:

  1. A user opens a browser which has a remote inspector server running.
  2. There is one tab open, on example.com.
  3. User navigates that tab to the remote inspector listing page.
    3.5 The listing page generates a response from the list of WebViews and
        lists "example.com" as the only result. The response is sent.
  4. The listing page is loaded in the WebView, and there is a listing for
     the existing WebView.
  5. A WebView attempting to inspect itself causes cyclic problems and
     should not be allowed.

In short, this is "Tab A" trying to remotely inspect "Tab A", which is
bad. Normal usage expects "Tab A" to remotely inspect "Tab B". And, although
it is possible, "Tab C" could then remotely inspect "Tab A" which is remotely
inspecting "Tab B", it doesn't make sense from a usability standpoint.

For those reasons, I'd like to prevent listing WebViews that are in a "remote"
inspector mode. The only way I can think of doing this currently is when
generating the listing page, check each WebView to see if they are in the
process of loading (or making a request) to something equivalent to
"localhost:port" which is the inspector server running in the browser.
This is very dirty.

Something that would make this easier, is to move remote inspector sessions
to a different scheme. Something like inspector://. Now, it would be much
easier to check if a WebView is "in a remote inspector mode" and should
not be listed. The inspector:// scheme would simply act like http://, but
its presence is much easier to detect.

Does this sound like a good idea?

An alternative solution would be to have a new dedicated window for remote
inspection, that has opt-out of being listed. Much like the existing local
inspector. We could add UI to the inspector that would allow it to provide
a listing of other pages it could switch to inspect.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list