[Webkit-unassigned] [Bug 237601] [GTK][WPE] Web Inspector: make it possible to use the remote inspector from other browsers

[bugzilla-daemon at webkit.org]

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

Adrian Perez <aperez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aperez at igalia.com

--- Comment #6 from Adrian Perez <aperez at igalia.com> ---
(In reply to Carlos Garcia Campos from comment #5)
> (In reply to Fujii Hironori from comment #3)
> > This reminds me the previous discussion (Bug 172966).
> > Does the current WebInspectorUI work nicely with non-WebKit browsers?
> > If not, do you have a plan to change WebInspectorUI for non-WebKit?
> 
> No, it doesn't work with non-WebKit browsers. Note that being able to use
> Safari on MacOS to inspect WPE is already a huge improvement. We still plan
> to try to make it work at least in chrome, and at least the basic
> functionality.

Making things work in Chromium is not much work, I have made a small patch
that seems to get the job done (I didn't do a lot of testing, there may be
still other changes needed, YMMV):

  https://o.perezdecastro.org/inspector-chromium.diff

The issue is that the inspector uses CSSStyleDeclaration.getPropertyCSSValue(),
which according to MDN is deprecated and implemented only in WebKit; the patch
linked above switches over to use Element.computedStyleMap() which the other
web engines implement (it's part of CSS Typed OM level 2).

In the case of Firefox, I have a small patch that adds a polyfill for
Element.scrollIntoViewIfNeeded() by using the “options” parameter to
Element.scrollIntoView() to achieve the same effect (this is part of
CSS OM View module): 

  https://o.perezdecastro.org/inspector-firefox.diff

While the patch above gets the inspector loaded in Firefox and many
things more or less working okay, there are still features that do not
work (I haven't looked at them yet) and in some places a few obvious
graphical glitches.

-- 
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/20220309/94f70704/attachment.htm>