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

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Joseph Pecoraro <joepeck at webkit.org>  2010-12-20 19:19:39 PST ---
Concerns / Comments / FIXMEs off of the top of my head:

  • Improve Listing Page:
    - Cull uninteresting webviews: Currently all WebViews show up in the listing.
      That includes Inspector web views and if you use the browser while remote
      debugging, you can even try to debug your own web view (doh).
    - Should WebView's opt-out or opt-in to remote debugging? I haven't decided yet.

  • Privacy / Security:
    - Respect private browsing, and disable this feature.
    - Possibly limit to just localhost connections early on?
    - We need to sanitize, or change, what we output on the listing page. Currently
      this dumps the document title / url on the listing page in a JavaScript string.
      This means injection of a single quote, or </script> may break the listing page.
      FIXME is included.

  • Remote versus Local Debugger
    - Currently the first inspector session to start has control. It may make more
      sense for a local session to always take priority, and to take control away
      from a remote session. If that is desired, then there would need to be a
      small changes otherwise. Currently, in that scenario, "open inspector" locally
      just trys to "bringToFront" the remote inspector.

  • Enable / Disable a different way?
    - Currently, I am using defaults and preferences changed to enable the server.
      However, apparently this caused "Safari Webpage Preview Fetcher" to try and
      create a web server, since it also uses Safari's preferences and handler?

  • Usability:
    - Discoverability of the feature, should probably be done at the browser level.
    - Sending error messages back to the remote side is not very good. For instance,
      if there is already a local debug session and a remote debug session is
      attempted. We prevent the remote session from starting, but the remote user gets
      no warning, just a mostly blank page. Many other error conditions have no
      user warning on the remote side.
    - "Slow scripts" executed on a remote frontend pop up a modal dialog on the
      backend page. This would make using the debugger impossible! See bug 46247,
      and bug 34303, and probably others.
    - There can be many other improvements. Such as sending screenshots or "fake
      rendering" what the page probably looks like in a remote debugger. Etc.

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