[Webkit-unassigned] [Bug 22551] [GTK] API to start inspector for a WebView
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 20 12:10:04 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=22551
------- Comment #14 from zuh at iki.fi 2009-04-20 12:10 PDT -------
(In reply to comment #13)
> (In reply to comment #12)
> > Well, and that being said, is there a reason for not only having the API to
> > open it in a specific page? I don't think that depends on anything, and we
> > could do just that unless somebody thinks having one parameter-less "open in
> > the default page" is a big win.
>
> I think Gustavo mainly didn't want to let the bug vanish rot, and after the
> question of choosing pages was raised nobody replied anymore.
>
> For what I want, we can have webkit_web_inspector_open (const gchar* page) if
> that works for you. Using a string to specify the page was suggested earlier
> and to me seems like the way to go.
It's slightly nasty, but does give a bit more future- and change-proof API.
So something like this perhaps:
/**
* webkit_web_inspector_inspect:
* @web_inspector: a #WebKitWebInspector
* @inspector_panel: a string identifying the panel to show
*
* Activates the #WebKitWebInspector and switches it to the specified inspector
* panel. The inspector is activated with the document node of the currently
* focused or the main frame of the associated #WebKitWebView. If the panel
* string is NULL or specifies an unkown panel, no switching will occur.
*
* Since: 1.1.6
**/
void webkit_web_inspector_inspect(WebKitWebInspector *web_inspector,
const gchar *inspector_panel)
followed by inspect_element(web_inspector, inspector_panel, dom_element) as
soon as the dom bindings are available.
If the above is ok, I'll redo the patch accordingly. Actually I started
already, but it's going to take few nights since someone forgot to add the 12
extra hours to a day so there's good time for feedback...
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list