[Webkit-unassigned] [Bug 172966] Remove legacy INSPECTOR_SERVER implementation

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jun 11 22:47:35 PDT 2017


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

--- Comment #25 from Carlos Garcia Campos <cgarcia at igalia.com> ---
(In reply to Don Olmstead from comment #24)
> (In reply to Carlos Garcia Campos from comment #17)
> > (In reply to Don Olmstead from comment #13)
> > > (In reply to Olivier Blin from comment #10)
> > > > (In reply to Michael Catanzaro from comment #8)
> > > > > (In reply to Olivier Blin from comment #7)
> > > > > > We are WPE users, and we know that in the set-top box market, quite some web
> > > > > > app developers are today connecting to the remote web inspector from a
> > > > > > Windows OS.
> > > > > 
> > > > > I really think compatibility with non-WebKit browsers should be a non-goal.
> > > > > That's really out there. If it works at all today with the WebSocket server,
> > > > > that's just due to luck.
> > > > 
> > > > Well, it would make web developers life a lot easier if it just worked from
> > > > Chrome.
> > > 
> > > From
> > > https://blogs.igalia.com/carlosgc/2017/05/03/webkitgtk-remote-debugging-in-2-
> > > 18/ it sounds like you couldn't even use Safari to do a remote debugging
> > > session. Is this correct? Our users are primarily developing on Macs.
> > 
> > Correct.
> 
> Ok well that's a pretty big deal breaker for us.

What browser do you currently use for remote debugging? I'm still surprised you could use a non-webkit browser, because it has been impossible for me lately due to the JavaScript features used by WebKit.

> Is there any way to have a cross-platform remote inspector?

You can use a linux virtual machine, I guess. In the case of Mac OS, I think you can build WebKitGTK+ with the quartz backend.

> If not I think
> we're going to ask to revert this and then enable the inspector server
> within wincairo.

Isn't WinCairo a WebKit1 port? The inspector server was in WebKit2, or do you mean only the changes in the inspector itself? I still don't understand why you can add you inspector server implementation to your downstream fork and not the inspector server itself too. You are still assuming you have to switch to the new remote inspector, but again, you don't have to.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170612/2833b8a4/attachment.html>


More information about the webkit-unassigned mailing list