webkit_user_content_manager_new ()

WebKitUserContentManager *
webkit_user_content_manager_new (void);

Creates a new user content manager.

Since: 2.6

webkit_user_content_manager_add_style_sheet ()

void
webkit_user_content_manager_add_style_sheet
                               (WebKitUserContentManager *manager,
                                WebKitUserStyleSheet *stylesheet);

Adds a WebKitUserStyleSheet to the given WebKitUserContentManager. The same WebKitUserStyleSheet can be reused with multiple WebKitUserContentManager instances.

Since: 2.6

webkit_user_content_manager_remove_all_style_sheets ()

void
webkit_user_content_manager_remove_all_style_sheets
                               (WebKitUserContentManager *manager);

Removes all user style sheets from the given WebKitUserContentManager.

Since: 2.6

webkit_user_content_manager_add_script ()

void
webkit_user_content_manager_add_script
                               (WebKitUserContentManager *manager,
                                WebKitUserScript *script);

Adds a WebKitUserScript to the given WebKitUserContentManager. The same WebKitUserScript can be reused with multiple WebKitUserContentManager instances.

Since: 2.6

webkit_user_content_manager_remove_all_scripts ()

void
webkit_user_content_manager_remove_all_scripts
                               (WebKitUserContentManager *manager);

Removes all user scripts from the given WebKitUserContentManager

Since: 2.6

webkit_user_content_manager_register_script_message_handler ()

gboolean
webkit_user_content_manager_register_script_message_handler
                               (WebKitUserContentManager *manager,
                                const gchar *name);

Registers a new user script message handler. After it is registered, scripts can use window.webkit.messageHandlers.<name>.postMessage(value) to send messages. Those messages are received by connecting handlers to the “script-message-received” signal. The handler name is used as the detail of the signal. To avoid race conditions between registering the handler name, and starting to receive the signals, it is recommended to connect to the signal *before* registering the handler name:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

WebKitWebView *view = webkit_web_view_new ();
WebKitUserContentManager *manager = webkit_web_view_get_user_content_manager ();
g_signal_connect (manager, "script-message-received::foobar",
                  G_CALLBACK (handle_script_message), NULL);
webkit_user_content_manager_register_script_message_handler (manager, "foobar");

Registering a script message handler will fail if the requested name has been already registered before.

Since: 2.8

webkit_user_content_manager_unregister_script_message_handler ()

void
webkit_user_content_manager_unregister_script_message_handler
                               (WebKitUserContentManager *manager,
                                const gchar *name);

Unregisters a previously registered message handler.

Note that this does *not* disconnect handlers for the “script-message-received” signal, they will be kept connected, but the signal will not be emitted unless the handler name is registered again.

See also webkit_user_content_manager_register_script_message_handler()

Since: 2.8

struct WebKitUserContentManager

struct WebKitUserContentManager;

The “script-message-received” signal

void
user_function (WebKitUserContentManager *manager,
               WebKitJavascriptResult   *js_result,
               gpointer                  user_data)

This signal is emitted when JavaScript in a web view calls

webkit_user_content_manager_register_script_message_handler()

Flags: Has Details

Since: 2.8