[Webkit-unassigned] [Bug 30773] [Qt] QWebInspector: improve QWebPage::webInspectorTriggered(QWebElement&) -> QWebInspector::show() connection
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Nov 3 01:12:44 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=30773
--- Comment #9 from Jocelyn Turcotte <jocelyn.turcotte at nokia.com> 2009-11-03 01:12:44 PDT ---
(In reply to comment #8)
> (In reply to comment #6)
> > It is possible to use the same web inspector for more pages?
>
> That's a good point, but I think we can handle that later without braking the
> current behavior.
>
> Later, we can add the signal webInspectorTriggered() and have
> setInspectedElement() to change the element. In that case, you will be able to
> use the same inspector for different pages.
>
> We can also add webInspectorTriggered() without the argument in the future.
The backend don't support this scenario. Moreover, the UI is not designed to
display information from more than one page at the same time. The javascript
console would also cause problems.
Behind the scene, the web inspector is tightly bound to WebCore's page and is
not an independent API.
What we could do is to keep states like the current displayed tab within the
QWebInspector and re-set this value when we do a setPage on a different
QWebPage.
--
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