WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
86823
[GTK] Allow to attach/detach the inspector in WebKit2
https://bugs.webkit.org/show_bug.cgi?id=86823
Summary
[GTK] Allow to attach/detach the inspector in WebKit2
Carlos Garcia Campos
Reported
2012-05-18 01:31:21 PDT
Currently attach/detach is not implemented, we always create a new window for the inspector, and the attach button does nothing.
Attachments
Patch
(25.52 KB, patch)
2012-05-18 01:57 PDT
,
Carlos Garcia Campos
gustavo
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Carlos Garcia Campos
Comment 1
2012-05-18 01:57:42 PDT
Created
attachment 142667
[details]
Patch
WebKit Review Bot
Comment 2
2012-05-18 02:01:50 PDT
Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See
http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API
Gustavo Noronha (kov)
Comment 3
2012-05-18 05:49:08 PDT
Comment on
attachment 142667
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=142667&action=review
> Source/WebKit2/UIProcess/API/gtk/WebKitWebViewBase.cpp:438 > - return FALSE; > + return TRUE;
These look like a somewhat unrelated fix. In the interest of better bisectability, can you land these three in a separate commit? rs=me on doing that
> Source/WebKit2/UIProcess/gtk/WebInspectorProxyGtk.cpp:156 > + // This method is called to decide whether to attach the inspector or not depending on whether > + // the inspector view fits into the window. Attach is implemented by the client, so return 0 > + // when the client doesn't implement attach, to make sure the inspector is never attached.
I don't understand this comment, who would return 0 here?
Carlos Garcia Campos
Comment 4
2012-05-18 06:01:00 PDT
(In reply to
comment #3
)
> (From update of
attachment 142667
[details]
) > View in context:
https://bugs.webkit.org/attachment.cgi?id=142667&action=review
> > > Source/WebKit2/UIProcess/API/gtk/WebKitWebViewBase.cpp:438 > > - return FALSE; > > + return TRUE; > > These look like a somewhat unrelated fix. In the interest of better bisectability, can you land these three in a separate commit? rs=me on doing that
It's actually related, before this patch, it doesn't really matter whether we return TRUE or FALSE, because the even has been handled by the view. Now, if you click on the inspector view, and the inspector propagates the event, it gets to the inspected web view. This is specially noticeable when scrolling in the inspector and the inspected view is scrolled too at the same time. In any case, I can split this if you want.
> > Source/WebKit2/UIProcess/gtk/WebInspectorProxyGtk.cpp:156 > > + // This method is called to decide whether to attach the inspector or not depending on whether > > + // the inspector view fits into the window. Attach is implemented by the client, so return 0 > > + // when the client doesn't implement attach, to make sure the inspector is never attached. > > I don't understand this comment, who would return 0 here?
oops, that comment doesn't make any sense, I forgot to remove it, it's part of another patch that I discarded.
Carlos Garcia Campos
Comment 5
2012-05-18 08:20:42 PDT
Committed
r117595
: <
http://trac.webkit.org/changeset/117595
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug