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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 12 00:18:16 PDT 2017


--- Comment #26 from Zan Dobersek <zan at falconsigh.net> ---
(In reply to Joseph Pecoraro from comment #15)
> > > 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.
> To add to this: The WebKit Web Inspector frontend frequently adopts many
> features soon after they are added to trunk WebKit / JavaScriptCore. Some of
> these features may not be implemented / supported by other browsers,
> including Chrome. We make no effort to ensure the frontend is cross browser
> compatibility given we are writing it only for WebKit.
> One example off the top of my head is we use `-webkit-canvas()` for
> popovers. I don't think any other browser implements this. In fact I think
> Chrome/Blink removed it years ago.

(In reply to Michael Catanzaro from comment #16)
> I know our web inspector required ES6 features at least a year before they
> were enabled in Chrome. I think you must have needed a significant amount of
> patches to keep web inspector working during this time, or maybe were just
> using a very old version of WebKit?

The WebSocket-based remote inspector did not work properly when not used from WPE, WebKitGTK+ or recent Safari (Technology Preview or a development build).

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/87937858/attachment-0001.html>

More information about the webkit-unassigned mailing list