Top |
WebKitDOMDocument *
webkit_web_page_get_dom_document (WebKitWebPage *web_page
);
Get the WebKitDOMDocument currently loaded in web_page
the WebKitDOMDocument currently loaded, or NULL
if no document is currently loaded.
[transfer none]
guint64
webkit_web_page_get_id (WebKitWebPage *web_page
);
Get the identifier of the WebKitWebPage
const gchar *
webkit_web_page_get_uri (WebKitWebPage *web_page
);
Returns the current active URI of web_page
.
You can monitor the active URI by connecting to the notify::uri
signal of web_page
.
WebKitFrame *
webkit_web_page_get_main_frame (WebKitWebPage *web_page
);
Returns the main frame of a WebKitWebPage.
Since: 2.2
WebKitWebEditor *
webkit_web_page_get_editor (WebKitWebPage *web_page
);
Gets the WebKitWebEditor of a WebKitWebPage.
Since: 2.10
Used to indicate a particular stage in form submission. See “will-submit-form”.
Since: 2.20
“uri”
property“uri” gchar *
The current active URI of the WebKitWebPage.
Flags: Read
Default value: NULL
“console-message-sent”
signalvoid user_function (WebKitWebPage *web_page, WebKitConsoleMessage *console_message, gpointer user_data)
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_message
contains information of the message.
web_page |
the WebKitWebPage on which the signal is emitted |
|
console_message |
||
user_data |
user data set when the signal handler was connected. |
Flags: Run Last
Since: 2.12
“context-menu”
signalgboolean user_function (WebKitWebPage *web_page, WebKitContextMenu *context_menu, WebKitWebHitTestResult *hit_test_result, gpointer user_data)
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 WebKitDOMNode at the coordinates of the
hit_test_result
. Otherwise, it's recommended to use “context-menu”
signal instead.
web_page |
the WebKitWebPage on which the signal is emitted |
|
context_menu |
the proposed WebKitContextMenu |
|
hit_test_result |
||
user_data |
user data set when the signal handler was connected. |
Flags: Run Last
Since: 2.8
“document-loaded”
signalvoid user_function (WebKitWebPage *web_page, gpointer user_data)
This signal is emitted when the DOM document of a WebKitWebPage has been loaded.
You can wait for this signal to get the DOM document with
webkit_web_page_get_dom_document()
.
web_page |
the WebKitWebPage on which the signal is emitted |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run Last
“form-controls-associated”
signalvoid user_function (WebKitWebPage *web_page, GPtrArray *elements, gpointer user_data)
Emitted after form elements (or form associated elements) are associated to a particular web page. This is useful to implement form auto filling for web pages where form fields are added dynamically. This signal might be emitted multiple times for the same web page.
Note that this signal could be also emitted when form controls are moved between forms. In
that case, the elements
array carries the list of those elements which have moved.
Clients should take a reference to the members of the elements
array if it is desired to
keep them alive after the signal handler returns.
web_page |
the WebKitWebPage on which the signal is emitted |
|
elements |
a GPtrArray of WebKitDOMElement with the list of forms in the page. |
[element-type WebKitDOMElement][transfer none] |
user_data |
user data set when the signal handler was connected. |
Flags: Run Last
Since: 2.16
“send-request”
signalgboolean user_function (WebKitWebPage *web_page, WebKitURIRequest *request, WebKitURIResponse *redirected_response, gpointer user_data)
This signal is emitted when request
is about to be sent to
the server. This signal can be used to modify the WebKitURIRequest
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.
web_page |
the WebKitWebPage on which the signal is emitted |
|
request |
||
redirected_response |
a WebKitURIResponse, or |
|
user_data |
user data set when the signal handler was connected. |
TRUE
to stop other handlers from being invoked for the event.
FALSE
to continue emission of the event.
Flags: Run Last
“will-submit-form”
signalvoid user_function (WebKitWebPage *web_page, WebKitDOMHTMLFormElement *form, WebKitFormSubmissionStep step, WebKitFrame *source_frame, WebKitFrame *target_frame, GPtrArray *text_field_names, GPtrArray *text_field_values, gpointer user_data)
This signal is emitted to indicate various points during form
submission. step
indicates the current stage of form submission.
If this signal is emitted with WEBKIT_FORM_SUBMISSION_WILL_SEND_DOM_EVENT
,
then the DOM submit event is about to be emitted. JavaScript code
may rely on the submit event to detect that the user has clicked
on a submit button, and to possibly cancel the form submission
before WEBKIT_FORM_SUBMISSION_WILL_COMPLETE
. However, beware
that, for historical reasons, the submit event is not emitted at
all if the form submission is triggered by JavaScript. For these
reasons, WEBKIT_FORM_SUBMISSION_WILL_SEND_DOM_EVENT
may not
be used to reliably detect whether a form will be submitted.
Instead, use it to detect if a user has clicked on a form's
submit button even if JavaScript later cancels the form
submission, or to read the values of the form's fields even if
JavaScript later clears certain fields before submitting. This
may be needed, for example, to implement a robust browser
password manager, as some misguided websites may use such
techniques to attempt to thwart password managers.
If this signal is emitted with WEBKIT_FORM_SUBMISSION_WILL_COMPLETE
,
the form will imminently be submitted. It can no longer be
cancelled. This event always occurs immediately before a form is
submitted to its target, so use this event to reliably detect
when a form is submitted. This event occurs after
WEBKIT_FORM_SUBMISSION_WILL_SEND_DOM_EVENT
if that event is
emitted.
web_page |
the WebKitWebPage on which the signal is emitted |
|
form |
the WebKitDOMHTMLFormElement to be submitted |
|
step |
a WebKitFormSubmissionEventType indicating the current stage of form submission |
|
source_frame |
the WebKitFrame containing the form to be submitted |
|
target_frame |
the WebKitFrame containing the form's target,
which may be the same as |
|
text_field_names |
names of the form's text fields. |
[element-type utf8][transfer none] |
text_field_values |
values of the form's text fields. |
[element-type utf8][transfer none] |
user_data |
user data set when the signal handler was connected. |
Flags: Run Last
Since: 2.20