[Webkit-unassigned] [Bug 157899] New: [GTK] Provide WebKitWebView::frame-loaded signal

[bugzilla-daemon at webkit.org]

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

            Bug ID: 157899
           Summary: [GTK] Provide WebKitWebView::frame-loaded signal
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Enhancement
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcrha at redhat.com
                CC: bugs-noreply at webkitgtk.org

While working on the Evolution port to the WebKit2, I realized that there is a problem when to attach DOM bindings, especially when the web view contains iframe-s (and these iframe-s can be formatted mail messages, which also contain iframe-s). The only current way of noticing when the loading was finished is to listen to WebKitWebView::load-event and add the bindings when the load_event == WEBKIT_LOAD_FINISHED, but it's a matter of luck whether the internal iframe-s will be loaded or not at that time.

Due to this, I propose a new signal to be added to the WebKitWebView with a name "frame-loaded", with a prototype:

    void
    frame_loaded (WebKitWebView *web_view,
                  const gchar *frame_src, /* 'src' attribute content of the loaded (i)frame */
                  const gchar *frame_id,  /* 'id' attribute content of the loaded (i)frame */
                  gpointer user_data)

which will be called whenever any (i)frame will be in a state equivalent of the load_event == WEBKIT_LOAD_FINISHED of the main WebKitWebView.
That way, the subscriber to this signal will know that everything is ready and the DOM bindings can be safely done on that particular frame.

I was told that you have a similar request from someone else already, but I didn't find it in the bugzilla (maybe I used wrong search term), thus I filled it myself.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160519/b55738af/attachment-0001.html>