| Top | |
|
|
|
WebKitAutomationSession represents an automation session of a WebKitWebContext. When a new session is requested, a WebKitAutomationSession is created and the signal WebKitWebContext::automation-started is emitted with the WebKitAutomationSession as argument. Then, the automation client can request the session to create a new WebKitWebView to interact with it. When this happens the signal “create-web-view” is emitted.
const char *
webkit_automation_session_get_id (WebKitAutomationSession *session);
Get the unique identifier of a WebKitAutomationSession
Since: 2.18
void webkit_automation_session_set_application_info (WebKitAutomationSession *session,WebKitApplicationInfo *info);
Set the application information to session
. This information will be used by the driver service
to match the requested capabilities with the actual application information. If this information
is not provided to the session when a new automation session is requested, the creation might fail
if the client requested a specific browser name or version. This will not have any effect when called
after the automation session has been fully created, so this must be called in the callback of
“automation-started” signal.
Since: 2.18
WebKitApplicationInfo *
webkit_automation_session_get_application_info
(WebKitAutomationSession *session);
Get the WebKitAutomationSession previously set with webkit_automation_session_set_application_info().
Since: 2.18
“create-web-view” signalWebKitWebView* user_function (WebKitAutomationSession *session, gpointer user_data)
This signal is emitted when the automation client requests a new browsing context to interact with it. The callback handler should return a WebKitWebView created with “is-controlled-by-automation” construct property enabled. The returned WebKitWebView could be an existing web view or a new one created and added to a new tab or window.
Flags: Run Last
Since: 2.18