SignalRun Lastconsole-SignalRun Lastcontext-Emitted before a context menu is displayed in the UI Process to
give the application a chance to customize the proposed menu,
build its own context menu or pass user data to the UI Process.
This signal is useful when the information available in the UI Process
is not enough to build or customize the context menu, for example, to
add menu entries depending on the node at the coordinates of the
hit_test_result. Otherwise, it's recommended to use WebKitWebView::context-menu
signal instead.
SignalRun Lastdocument-This signal is emitted when the DOM document of a WebKitWebProcessExtension.WebPage has been loaded.
You can wait for this signal to get the DOM document
SignalRun Lastsend-This signal is emitted when request is about to be sent to
the server. This signal can be used to modify the WebKitWebProcessExtension.URIRequest
that will be sent to the server. You can also cancel the resource load
operation by connecting to this signal and returning true.
In case of a server redirection this signal is
emitted again with the request argument containing the new
request to be sent to the server due to the redirection and the
redirected_response parameter containing the response
received by the server for the initial request.
Modifications to the WebKitWebProcessExtension.URIRequest and its associated Soup.MessageHeaders will be taken into account when the request is sent over the network.
SignalRun Lastuser-This signal is emitted when a WebKitWebProcessExtension.UserMessage is received from the
WebKitWebView corresponding to web_page. You can reply to the message
using webkit_user_message_send_reply().
You can handle the user message asynchronously by calling g_object_ref() on
message and returning true. If the last reference of message is removed
and the message has been replied, the operation in the WebKitWebView will
finish with error WebKitWebProcessExtension.UserMessageError.USER_MESSAGE_UNHANDLED_MESSAGE.
SignalDetailedActionRun FirstnotifyThe notify signal is emitted on an object when one of its properties has
its value set through g_object_set_property(), g_object_set(), et al.
Note that getting this signal doesn’t itself guarantee that the value of
the property has actually changed. When it is emitted is determined by the
derived GObject class. If the implementor did not create the property with
GObject.ParamFlags.EXPLICIT_NOTIFY, then any call to g_object_set_property() results
in ::notify being emitted, even if the new value is the same as the old.
If they did pass GObject.ParamFlags.EXPLICIT_NOTIFY, then this signal is emitted only
when they explicitly call g_object_notify() or g_object_notify_by_pspec(),
and common practice is to do that only when the value has actually changed.
This signal is typically used to obtain change notification for a
single property, by specifying the property name as a detail in the
g_signal_connect() call, like this:
g_signal_connect (text_view->buffer, "notify::paste-target-list",
G_CALLBACK (gtk_text_view_target_list_notify),
text_view)
It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.
Emitted when a message is sent to the console. This can be a message produced by the use of JavaScript console API, a JavaScript exception, a security error or other errors, warnings, debug or log messages. The
console_messagecontains information of the message.