WebKit2.AutomationSession¶
- Subclasses:
None
Methods¶
- Inherited:
- Structs:
|
|
|
Virtual Methods¶
- Inherited:
Properties¶
Name |
Type |
Flags |
Short Description |
|---|---|---|---|
r/w/co |
Signals¶
- Inherited:
Name |
Short Description |
|---|---|
This signal is emitted when the automation client requests a new browsing context to interact with it. |
|
This signal is emitted when the given automation session is about to finish. |
Fields¶
- Inherited:
Name |
Type |
Access |
Description |
|---|---|---|---|
parent |
r |
Class Details¶
- class WebKit2.AutomationSession(**kwargs)¶
- Bases:
- Abstract:
No
- Structure:
Automation Session.
WebKit2.AutomationSessionrepresents an automation session of aWebKit2.WebContext. When a new session is requested, aWebKit2.AutomationSessionis created and the signalWebKit2.WebContext::automation-startedis emitted with theWebKit2.AutomationSessionas argument. Then, the automation client can request the session to create a newWebKit2.WebViewto interact with it. When this happens the signalWebKit2.AutomationSession::create-web-viewis emitted.New in version 2.18.
- get_application_info()¶
- Returns:
the
WebKit2.AutomationSessionof self, orNoneif no one has been set.- Return type:
Get the the previously set
WebKit2.AutomationSession.Get the
WebKit2.AutomationSessionpreviously set withWebKit2.AutomationSession.set_application_info().New in version 2.18.
- get_id()¶
- Returns:
the unique identifier of self
- Return type:
Get the unique identifier of a
WebKit2.AutomationSessionNew in version 2.18.
- set_application_info(info)¶
- Parameters:
info (
WebKit2.ApplicationInfo) – aWebKit2.ApplicationInfo
Set the application information to self.
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
WebKit2.WebContext::automation-startedsignal.New in version 2.18.
Signal Details¶
- WebKit2.AutomationSession.signals.create_web_view(automation_session)¶
- Signal Name:
create-web-view- Flags:
- Parameters:
automation_session (
WebKit2.AutomationSession) – The object which received the signal- Returns:
a
WebKit2.WebViewwidget.- Return type:
This signal is emitted when the automation client requests a new browsing context to interact with it. The callback handler should return a
WebKit2.WebViewcreated withWebKit2.WebView:is-controlled-by-automationconstruct property enabled andWebKit2.WebView:automation-presentation-typeconstruct property set if needed.If the signal is emitted with “tab” detail, the returned
WebKit2.WebViewshould be a new web view added to a new tab of the current browsing context window. If the signal is emitted with “window” detail, the returnedWebKit2.WebViewshould be a new web view added to a new window. When creating a new web view and there’s an active browsing context, the new window or tab shouldn’t be focused.New in version 2.18.
- WebKit2.AutomationSession.signals.will_close(automation_session)¶
- Signal Name:
will-close- Flags:
- Parameters:
automation_session (
WebKit2.AutomationSession) – The object which received the signal
This signal is emitted when the given automation session is about to finish. It allows clients to perform any cleanup tasks before the session is destroyed.
New in version 2.46.