[Webkit-unassigned] [Bug 64297] [Qt][WK2] Add the Web Inspector to WebKit2
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Sep 1 06:43:16 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=64297
--- Comment #84 from Jocelyn Turcotte <jocelyn.turcotte at nokia.com> 2011-09-01 06:43:14 PST ---
(From update of attachment 105850)
View in context: https://bugs.webkit.org/attachment.cgi?id=105850&action=review
> Source/WebKit2/UIProcess/qt/QtWebPageProxy.cpp:751
> +void QtWebPageProxy::setWebInspectorEnabled(bool enable)
> +{
> + if (enable)
> + m_webPageProxy->inspector()->show();
> + else
> + m_webPageProxy->inspector()->close();
> +}
Before trying to create APIs blindly by binding to Qt what is already in WebKit2 we should ask ourself how is the inspector going to be used, and how we can make it both easy to use and flexible.
Especially for the touch view, a cross-device remote inspector is necessary, and this is the main concern for WebKit2 and Qt5 right now.
In the end we want QtCreator or any desktop front-end of the developer to have the ability to inspect a page on a development device. I think that the desktop should also be considered but that it's way of doing things should be as near as possible to the way of the touch view since it will always be simpler.
I think that magically popping a top level window is not the right approach for those reasons, and we should focus first on designing remote inspection before exposing API. Local inspection within the MiniBrowser could then just use the remote channel and pop the top level window itself.
--
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