### Class

# Devhelp AssistantView

#### Description

    class Devhelp.AssistantView : WebKit2.WebView
      implements Atk.ImplementorIface, Gtk.Buildable {
      /* No available fields */
    }

No description available.

#### Ancestors

- WebKitWebView
- WebKitWebViewBase
- GtkContainer
- GtkWidget
- GInitiallyUnowned
- GObject

#### Implements

- AtkImplementorIface
- GtkBuildable

#### Constructors

###### dh_assistant_view_new

No description available.

#### Instance methods

###### dh_assistant_view_search

Search for `str` in the current assistant view.

###### dh_assistant_view_set_link

Open `link` in the assistant view, if `NULL` the view will be blanked.

##### Methods inherited from WebKitWebView (89)

Please see WebKitWebView for a full list of methods.

##### Methods inherited from GtkContainer (33)

Please see GtkContainer for a full list of methods.

##### Methods inherited from GtkWidget (263)

Please see GtkWidget for a full list of methods.

##### Methods inherited from GObject (43)

Please see GObject for a full list of methods.

##### Methods inherited from GtkBuildable (10)

###### gtk_buildable_add_child

Adds a child to `buildable`. `type` is an optional string describing how the child should be added.

###### gtk_buildable_construct_child

Constructs a child of `buildable` with the name `name`.

###### gtk_buildable_custom_finished

This is similar to `gtk_buildable_parser_finished()` but is called once for each custom tag handled by the `buildable`.

###### gtk_buildable_custom_tag_end

This is called at the end of each custom element handled by the buildable.

###### gtk_buildable_custom_tag_start

This is called for each unknown element under `<child>`.

###### gtk_buildable_get_internal_child

Get the internal child called `childname` of the `buildable` object.

###### gtk_buildable_get_name

Gets the name of the `buildable` object.

###### gtk_buildable_parser_finished

Called when the builder finishes the parsing of a [GtkBuilder UI definition][BUILDER-UI]. Note that this will be called once for each time `gtk_builder_add_from_file()` or `gtk_builder_add_from_string()` is called on a builder.

###### gtk_buildable_set_buildable_property

Sets the property name `name` to `value` on the `buildable` object.

###### gtk_buildable_set_name

Sets the name of the `buildable` object.

#### Properties

##### Properties inherited from WebKitWebView (24)

###### WebKit2.WebView:automation-presentation-type

The `WebKitAutomationBrowsingContextPresentation` of `WebKitWebView`. This should only be used when creating a new `WebKitWebView` as a response to `WebKitAutomationSession::create-web-view` signal request. If the new WebView was added to a new tab of current browsing context window `WEBKIT_AUTOMATION_BROWSING_CONTEXT_PRESENTATION_TAB` should be used.

###### WebKit2.WebView:camera-capture-state

Capture state of the camera device. Whenever the user grants a media-request sent by the web page, requesting video capture capabilities (`navigator.mediaDevices.getUserMedia({video: true})`) this property will be set to `WEBKIT_MEDIA_CAPTURE_STATE_ACTIVE`.

###### WebKit2.WebView:default-content-security-policy

The default Content-Security-Policy used by the webview as if it were set by an HTTP header.

###### WebKit2.WebView:display-capture-state

Capture state of the display device. Whenever the user grants a media-request sent by the web page, requesting screencasting capabilities (`navigator.mediaDevices.getDisplayMedia() this property will be set to`WEBKIT_MEDIA_CAPTURE_STATE_ACTIVE`.

###### WebKit2.WebView:editable

Whether the pages loaded inside `WebKitWebView` are editable. For more information see webkit_web_view_set_editable().

###### WebKit2.WebView:estimated-load-progress

An estimate of the percent completion for the current loading operation. This value will range from 0.0 to 1.0 and, once a load completes, will remain at 1.0 until a new load starts, at which point it will be reset to 0.0. The value is an estimate based on the total number of bytes expected to be received for a document, including all its possible subresources and child documents.

###### WebKit2.WebView:favicon

The favicon currently associated to the `WebKitWebView`. See `webkit_web_view_get_favicon()` for more details.

###### WebKit2.WebView:is-controlled-by-automation

Whether the `WebKitWebView` is controlled by automation tools (e.g. WebDriver, Selenium). This is required for views returned as a response to `WebKitAutomationSession::create-web-view` signal, alongside any view you want to control during an automation session.

###### WebKit2.WebView:is-ephemeral

Whether the `WebKitWebView` is ephemeral. An ephemeral web view never writes website data to the client storage, no matter what `WebKitWebsiteDataManager` its context is using. This is normally used to implement private browsing mode. This is a `G_PARAM_CONSTRUCT_ONLY` property, so you have to create an ephemeral `WebKitWebView` and it can’t be changed. The ephemeral `WebKitWebsiteDataManager` created for the `WebKitWebView` will inherit the network settings from the `WebKitWebContext`‘s `WebKitWebsiteDataManager`. To use different settings you can get the `WebKitWebsiteDataManager` with `webkit_web_view_get_website_data_manager()` and set the new ones. Note that all `WebKitWebView`s created with an ephemeral `WebKitWebContext` will be ephemeral automatically. See also webkit_web_context_new_ephemeral().

###### WebKit2.WebView:is-loading

Whether the `WebKitWebView` is currently loading a page. This property becomes `TRUE` as soon as a new load operation is requested and before the `WebKitWebView::load-changed` signal is emitted with `WEBKIT_LOAD_STARTED` and at that point the active URI is the requested one. When the load operation finishes the property is set to `FALSE` before `WebKitWebView::load-changed` is emitted with `WEBKIT_LOAD_FINISHED`.

###### WebKit2.WebView:is-muted

Whether the `WebKitWebView` audio is muted. When `TRUE`, audio is silenced. It may still be playing, i.e. `WebKitWebView:is-playing-audio` may be `TRUE`.

###### WebKit2.WebView:is-playing-audio

Whether the `WebKitWebView` is currently playing audio from a page. This property becomes `TRUE` as soon as web content starts playing any kind of audio. When a page is no longer playing any kind of sound, the property is set back to `FALSE`.

###### WebKit2.WebView:is-web-process-responsive

Whether the web process currently associated to the `WebKitWebView` is responsive.

###### WebKit2.WebView:microphone-capture-state

Capture state of the microphone device. Whenever the user grants a media-request sent by the web page, requesting audio capture capabilities (`navigator.mediaDevices.getUserMedia({audio: true})`) this property will be set to `WEBKIT_MEDIA_CAPTURE_STATE_ACTIVE`.

###### WebKit2.WebView:page-id

The identifier of the `WebKitWebPage` corresponding to the `WebKitWebView`.

###### WebKit2.WebView:related-view

The related `WebKitWebView` used when creating the view to share the same web process and network session. This property is not readable because the related web view is only valid during the object construction.

###### WebKit2.WebView:settings

The `WebKitSettings` of the view.

###### WebKit2.WebView:title

The main frame document title of this `WebKitWebView`. If the title has not been received yet, it will be `NULL`.

###### WebKit2.WebView:uri

The current active URI of the `WebKitWebView`. See `webkit_web_view_get_uri()` for more details.

###### WebKit2.WebView:user-content-manager

The `WebKitUserContentManager` of the view.

###### WebKit2.WebView:web-context

The `WebKitWebContext` of the view.

###### WebKit2.WebView:web-extension-mode

This configures `web_view` to treat the content as a WebExtension.

###### WebKit2.WebView:website-policies

The `WebKitWebsitePolicies` for the view.

###### WebKit2.WebView:zoom-level

The zoom level of the `WebKitWebView` content. See `webkit_web_view_set_zoom_level()` for more details.

##### Properties inherited from GtkContainer (3)

###### Gtk.Container:border-width

No description available.

###### Gtk.Container:child

No description available.

###### Gtk.Container:resize-mode

No description available.

##### Properties inherited from GtkWidget (39)

###### Gtk.Widget:app-paintable

No description available.

###### Gtk.Widget:can-default

No description available.

###### Gtk.Widget:can-focus

No description available.

###### Gtk.Widget:composite-child

No description available.

###### Gtk.Widget:double-buffered

Whether the widget is double buffered.

###### Gtk.Widget:events

No description available.

###### Gtk.Widget:expand

Whether to expand in both directions. Setting this sets both `GtkWidget:hexpand` and `GtkWidget:vexpand`.

###### Gtk.Widget:focus-on-click

Whether the widget should grab focus when it is clicked with the mouse.

###### Gtk.Widget:halign

How to distribute horizontal space if widget gets extra space, see `GtkAlign`.

###### Gtk.Widget:has-default

No description available.

###### Gtk.Widget:has-focus

No description available.

###### Gtk.Widget:has-tooltip

Enables or disables the emission of `GtkWidget::query-tooltip` on `widget`. A value of `TRUE` indicates that `widget` can have a tooltip, in this case the widget will be queried using `GtkWidget::query-tooltip` to determine whether it will provide a tooltip or not.

###### Gtk.Widget:height-request

No description available.

###### Gtk.Widget:hexpand

Whether to expand horizontally. See gtk_widget_set_hexpand().

###### Gtk.Widget:hexpand-set

Whether to use the `GtkWidget:hexpand` property. See gtk_widget_get_hexpand_set().

###### Gtk.Widget:is-focus

No description available.

###### Gtk.Widget:margin

Sets all four sides’ margin at once. If read, returns max margin on any side.

###### Gtk.Widget:margin-bottom

Margin on bottom side of widget.

###### Gtk.Widget:margin-end

Margin on end of widget, horizontally. This property supports left-to-right and right-to-left text directions.

###### Gtk.Widget:margin-left

Margin on left side of widget.

###### Gtk.Widget:margin-right

Margin on right side of widget.

###### Gtk.Widget:margin-start

Margin on start of widget, horizontally. This property supports left-to-right and right-to-left text directions.

###### Gtk.Widget:margin-top

Margin on top side of widget.

###### Gtk.Widget:name

No description available.

###### Gtk.Widget:no-show-all

No description available.

###### Gtk.Widget:opacity

The requested opacity of the widget. See `gtk_widget_set_opacity()` for more details about window opacity.

###### Gtk.Widget:parent

No description available.

###### Gtk.Widget:receives-default

No description available.

###### Gtk.Widget:scale-factor

The scale factor of the widget. See `gtk_widget_get_scale_factor()` for more details about widget scaling.

###### Gtk.Widget:sensitive

No description available.

###### Gtk.Widget:style

The style of the widget, which contains information about how it will look (colors, etc).

###### Gtk.Widget:tooltip-markup

Sets the text of tooltip to be the given string, which is marked up with the [Pango text markup language][PangoMarkupFormat]. Also see gtk_tooltip_set_markup().

###### Gtk.Widget:tooltip-text

Sets the text of tooltip to be the given string.

###### Gtk.Widget:valign

How to distribute vertical space if widget gets extra space, see `GtkAlign`.

###### Gtk.Widget:vexpand

Whether to expand vertically. See gtk_widget_set_vexpand().

###### Gtk.Widget:vexpand-set

Whether to use the `GtkWidget:vexpand` property. See gtk_widget_get_vexpand_set().

###### Gtk.Widget:visible

No description available.

###### Gtk.Widget:width-request

No description available.

###### Gtk.Widget:window

The widget’s window if it is realized, `NULL` otherwise.

#### Signals

###### Devhelp.AssistantView::open-uri

No description available.

##### Signals inherited from WebKitWebView (28)

###### WebKitWebView::authenticate

This signal is emitted when the user is challenged with HTTP authentication. To let the application access or supply the credentials as well as to allow the client application to either cancel the request or perform the authentication, the signal will pass an instance of the `WebKitAuthenticationRequest` in the `request` argument. To handle this signal asynchronously you should keep a ref of the request and return `TRUE`. To disable HTTP authentication entirely, connect to this signal and simply return `TRUE`.

###### WebKitWebView::close

Emitted when closing a `WebKitWebView` is requested. This occurs when a call is made from JavaScript’s <function>window.close</function> function or after trying to close the `web_view` with webkit_web_view_try_close(). It is the owner’s responsibility to handle this signal to hide or destroy the `WebKitWebView`, if necessary.

###### WebKitWebView::context-menu

Emitted when a context menu is about to be displayed to give the application a chance to customize the proposed menu, prevent the menu from being displayed, or build its own context menu. <itemizedlist> <listitem><para> To customize the proposed menu you can use webkit_context_menu_prepend(), `webkit_context_menu_append()` or `webkit_context_menu_insert()` to add new `WebKitContextMenuItem`s to `context_menu`, `webkit_context_menu_move_item()` to reorder existing items, or `webkit_context_menu_remove()` to remove an existing item. The signal handler should return `FALSE`, and the menu represented by `context_menu` will be shown. </para></listitem> <listitem><para> To prevent the menu from being displayed you can just connect to this signal and return `TRUE` so that the proposed menu will not be shown. </para></listitem> <listitem><para> To build your own menu, you can remove all items from the proposed menu with webkit_context_menu_remove_all(), add your own items and return `FALSE` so that the menu will be shown. You can also ignore the proposed `WebKitContextMenu`, build your own `GtkMenu` and return `TRUE` to prevent the proposed menu from being shown. </para></listitem> <listitem><para> If you just want the default menu to be shown always, simply don’t connect to this signal because showing the proposed context menu is the default behaviour. </para></listitem> </itemizedlist>.

###### WebKitWebView::context-menu-dismissed

Emitted after `WebKitWebView::context-menu` signal, if the context menu is shown, to notify that the context menu is dismissed.

###### WebKitWebView::create

Emitted when the creation of a new `WebKitWebView` is requested. If this signal is handled the signal handler should return the newly created `WebKitWebView`.

###### WebKitWebView::decide-policy

This signal is emitted when WebKit is requesting the client to decide a policy decision, such as whether to navigate to a page, open a new window or whether or not to download a resource. The `WebKitNavigationPolicyDecision` passed in the `decision` argument is a generic type, but should be casted to a more specific type when making the decision. For example:.

###### WebKitWebView::enter-fullscreen

Emitted when JavaScript code calls <function>element.webkitRequestFullScreen</function>. If the signal is not handled the `WebKitWebView` will proceed to full screen its top level window. This signal can be used by client code to request permission to the user prior doing the full screen transition and eventually prepare the top-level window (e.g. hide some widgets that would otherwise be part of the full screen window).

###### WebKitWebView::insecure-content-detected

Prior to 2.46, this signal was emitted when insecure content was loaded in a secure content. Since 2.46, this signal is generally no longer emitted.

###### WebKitWebView::leave-fullscreen

Emitted when the `WebKitWebView` is about to restore its top level window out of its full screen state. This signal can be used by client code to restore widgets hidden during the `WebKitWebView::enter-fullscreen` stage for instance.

###### WebKitWebView::load-changed

Emitted when a load operation in `web_view` changes. The signal is always emitted with `WEBKIT_LOAD_STARTED` when a new load request is made and `WEBKIT_LOAD_FINISHED` when the load finishes successfully or due to an error. When the ongoing load operation fails `WebKitWebView::load-failed` signal is emitted before `WebKitWebView::load-changed` is emitted with `WEBKIT_LOAD_FINISHED`. If a redirection is received from the server, this signal is emitted with `WEBKIT_LOAD_REDIRECTED` after the initial emission with `WEBKIT_LOAD_STARTED` and before `WEBKIT_LOAD_COMMITTED`. When the page content starts arriving the signal is emitted with `WEBKIT_LOAD_COMMITTED` event.

###### WebKitWebView::load-failed

Emitted when an error occurs during a load operation. If the error happened when starting to load data for a page `load_event` will be `WEBKIT_LOAD_STARTED`. If it happened while loading a committed data source `load_event` will be `WEBKIT_LOAD_COMMITTED`. Since a load error causes the load operation to finish, the signal WebKitWebView::load-changed will always be emitted with `WEBKIT_LOAD_FINISHED` event right after this one.

###### WebKitWebView::load-failed-with-tls-errors

Emitted when a TLS error occurs during a load operation. To allow an exception for this `certificate` and the host of `failing_uri` use webkit_web_context_allow_tls_certificate_for_host().

###### WebKitWebView::mouse-target-changed

This signal is emitted when the mouse cursor moves over an element such as a link, image or a media element. To determine what type of element the mouse cursor is over, a Hit Test is performed on the current mouse coordinates and the result is passed in the `hit_test_result` argument. The `modifiers` argument is a bitmask of `GdkModifierType` flags indicating the state of modifier keys. The signal is emitted again when the mouse is moved out of the current element with a new `hit_test_result`.

###### WebKitWebView::permission-request

This signal is emitted when WebKit is requesting the client to decide about a permission request, such as allowing the browser to switch to fullscreen mode, sharing its location or similar operations.

###### WebKitWebView::print

Emitted when printing is requested on `web_view`, usually by a JavaScript call, before the print dialog is shown. This signal can be used to set the initial print settings and page setup of `print_operation` to be used as default values in the print dialog. You can call `webkit_print_operation_set_print_settings()` and `webkit_print_operation_set_page_setup()` and then return `FALSE` to propagate the event so that the print dialog is shown.

###### WebKitWebView::query-permission-state

This signal allows the User-Agent to respond to permission requests for powerful features, as specified by the Permissions W3C Specification. You can reply to the query using webkit_permission_state_query_finish().

###### WebKitWebView::ready-to-show

Emitted after `WebKitWebView::create` on the newly created `WebKitWebView` when it should be displayed to the user. When this signal is emitted all the information about how the window should look, including size, position, whether the location, status and scrollbars should be displayed, is already set on the `WebKitWindowProperties` of `web_view`. See also webkit_web_view_get_window_properties().

###### WebKitWebView::resource-load-started

Emitted when a new resource is going to be loaded. The `request` parameter contains the `WebKitURIRequest` that will be sent to the server. You can monitor the load operation by connecting to the different signals of `resource`.

###### WebKitWebView::run-as-modal

Emitted after `WebKitWebView::ready-to-show` on the newly created `WebKitWebView` when JavaScript code calls <function>window.showModalDialog</function>. The purpose of this signal is to allow the client application to prepare the new view to behave as modal. Once the signal is emitted a new main loop will be run to block user interaction in the parent `WebKitWebView` until the new dialog is closed.

###### WebKitWebView::run-color-chooser

This signal is emitted when the user interacts with a HTML element, requesting from WebKit to show a dialog to select a color. To let the application know the details of the color chooser, as well as to allow the client application to either cancel the request or perform an actual color selection, the signal will pass an instance of the `WebKitColorChooserRequest` in the `request` argument.

###### WebKitWebView::run-file-chooser

This signal is emitted when the user interacts with a HTML element, requesting from WebKit to show a dialog to select one or more files to be uploaded. To let the application know the details of the file chooser, as well as to allow the client application to either cancel the request or perform an actual selection of files, the signal will pass an instance of the `WebKitFileChooserRequest` in the `request` argument.

###### WebKitWebView::script-dialog

Emitted when JavaScript code calls <function>window.alert</function>, <function>window.confirm</function> or <function>window.prompt</function>, or when <function>onbeforeunload</function> event is fired. The `dialog` parameter should be used to build the dialog. If the signal is not handled a different dialog will be built and shown depending on the dialog type: <itemizedlist> <listitem><para> `WEBKIT_SCRIPT_DIALOG_ALERT`: message dialog with a single Close button. </para></listitem> <listitem><para> `WEBKIT_SCRIPT_DIALOG_CONFIRM`: message dialog with OK and Cancel buttons. </para></listitem> <listitem><para> `WEBKIT_SCRIPT_DIALOG_PROMPT`: message dialog with OK and Cancel buttons and a text entry with the default text. </para></listitem> <listitem><para> `WEBKIT_SCRIPT_DIALOG_BEFORE_UNLOAD_CONFIRM`: message dialog with Stay and Leave buttons. </para></listitem> </itemizedlist>.

###### WebKitWebView::show-notification

This signal is emitted when a notification should be presented to the user. The `notification` is kept alive until either: 1) the web page cancels it or 2) a navigation happens.

###### WebKitWebView::show-option-menu

This signal is emitted when a select element in `web_view` needs to display a dropdown menu. This signal can be used to show a custom menu, using `menu` to get the details of all items that should be displayed. The area of the element in the `WebKitWebView` is given as `rectangle` parameter, it can be used to position the menu. If this was triggered by a user interaction, like a mouse click, `event` parameter provides the `GdkEvent`. To handle this signal asynchronously you should keep a ref of the `menu`.

###### WebKitWebView::submit-form

This signal is emitted when a form is about to be submitted. The `request` argument passed contains information about the text fields of the form. This is typically used to store login information that can be used later to pre-fill the form. The form will not be submitted until `webkit_form_submission_request_submit()` is called.

###### WebKitWebView::user-message-received

This signal is emitted when a `WebKitUserMessage` is received from the `WebKitWebPage` corresponding to `web_view`. You can reply to the message using webkit_user_message_send_reply().

###### WebKitWebView::web-process-crashed

This signal is emitted when the web process crashes.

###### WebKitWebView::web-process-terminated

This signal is emitted when the web process terminates abnormally due to `reason`.

##### Signals inherited from GtkContainer (4)

###### GtkContainer::add

No description available.

###### GtkContainer::check-resize

No description available.

###### GtkContainer::remove

No description available.

###### GtkContainer::set-focus-child

No description available.

##### Signals inherited from GtkWidget (69)

###### GtkWidget::accel-closures-changed

No description available.

###### GtkWidget::button-press-event

The ::button-press-event signal will be emitted when a button (typically from a mouse) is pressed.

###### GtkWidget::button-release-event

The ::button-release-event signal will be emitted when a button (typically from a mouse) is released.

###### GtkWidget::can-activate-accel

Determines whether an accelerator that activates the signal identified by `signal_id` can currently be activated. This signal is present to allow applications and derived widgets to override the default `GtkWidget` handling for determining whether an accelerator can be activated.

###### GtkWidget::child-notify

The ::child-notify signal is emitted for each [child property][child-properties] that has changed on an object. The signal’s detail holds the property name.

###### GtkWidget::composited-changed

The ::composited-changed signal is emitted when the composited status of `widgets` screen changes. See gdk_screen_is_composited().

###### GtkWidget::configure-event

The ::configure-event signal will be emitted when the size, position or stacking of the `widget`‘s window has changed.

###### GtkWidget::damage-event

Emitted when a redirected window belonging to `widget` gets drawn into. The region/area members of the event shows what area of the redirected drawable was drawn into.

###### GtkWidget::delete-event

The ::delete-event signal is emitted if a user requests that a toplevel window is closed. The default handler for this signal destroys the window. Connecting `gtk_widget_hide_on_delete()` to this signal will cause the window to be hidden instead, so that it can later be shown again without reconstructing it.

###### GtkWidget::destroy

Signals that all holders of a reference to the widget should release the reference that they hold. May result in finalization of the widget if all references are released.

###### GtkWidget::destroy-event

The ::destroy-event signal is emitted when a `GdkWindow` is destroyed. You rarely get this signal, because most widgets disconnect themselves from their window before they destroy it, so no widget owns the window at destroy time.

###### GtkWidget::direction-changed

The ::direction-changed signal is emitted when the text direction of a widget changes.

###### GtkWidget::drag-begin

The ::drag-begin signal is emitted on the drag source when a drag is started. A typical reason to connect to this signal is to set up a custom drag icon with e.g. gtk_drag_source_set_icon_pixbuf().

###### GtkWidget::drag-data-delete

The ::drag-data-delete signal is emitted on the drag source when a drag with the action `GDK_ACTION_MOVE` is successfully completed. The signal handler is responsible for deleting the data that has been dropped. What “delete” means depends on the context of the drag operation.

###### GtkWidget::drag-data-get

The ::drag-data-get signal is emitted on the drag source when the drop site requests the data which is dragged. It is the responsibility of the signal handler to fill `data` with the data in the format which is indicated by `info`. See `gtk_selection_data_set()` and gtk_selection_data_set_text().

###### GtkWidget::drag-data-received

The ::drag-data-received signal is emitted on the drop site when the dragged data has been received. If the data was received in order to determine whether the drop will be accepted, the handler is expected to call `gdk_drag_status()` and not finish the drag. If the data was received in response to a `GtkWidget::drag-drop` signal (and this is the last target to be received), the handler for this signal is expected to process the received data and then call gtk_drag_finish(), setting the `success` parameter depending on whether the data was processed successfully.

###### GtkWidget::drag-drop

The ::drag-drop signal is emitted on the drop site when the user drops the data onto the widget. The signal handler must determine whether the cursor position is in a drop zone or not. If it is not in a drop zone, it returns `FALSE` and no further processing is necessary. Otherwise, the handler returns `TRUE`. In this case, the handler must ensure that `gtk_drag_finish()` is called to let the source know that the drop is done. The call to `gtk_drag_finish()` can be done either directly or in a `GtkWidget::drag-data-received` handler which gets triggered by calling `gtk_drag_get_data()` to receive the data for one or more of the supported targets.

###### GtkWidget::drag-end

The ::drag-end signal is emitted on the drag source when a drag is finished. A typical reason to connect to this signal is to undo things done in `GtkWidget::drag-begin`.

###### GtkWidget::drag-failed

The ::drag-failed signal is emitted on the drag source when a drag has failed. The signal handler may hook custom code to handle a failed DnD operation based on the type of error, it returns `TRUE` is the failure has been already handled (not showing the default “drag operation failed” animation), otherwise it returns `FALSE`.

###### GtkWidget::drag-leave

The ::drag-leave signal is emitted on the drop site when the cursor leaves the widget. A typical reason to connect to this signal is to undo things done in `GtkWidget::drag-motion`, e.g. undo highlighting with gtk_drag_unhighlight().

###### GtkWidget::drag-motion

The ::drag-motion signal is emitted on the drop site when the user moves the cursor over the widget during a drag. The signal handler must determine whether the cursor position is in a drop zone or not. If it is not in a drop zone, it returns `FALSE` and no further processing is necessary. Otherwise, the handler returns `TRUE`. In this case, the handler is responsible for providing the necessary information for displaying feedback to the user, by calling gdk_drag_status().

###### GtkWidget::draw

This signal is emitted when a widget is supposed to render itself. The `widget`‘s top left corner must be painted at the origin of the passed in context and be sized to the values returned by `gtk_widget_get_allocated_width()` and gtk_widget_get_allocated_height().

###### GtkWidget::enter-notify-event

The ::enter-notify-event will be emitted when the pointer enters the `widget`‘s window.

###### GtkWidget::event

The GTK+ main loop will emit three signals for each GDK event delivered to a widget: one generic ::event signal, another, more specific, signal that matches the type of event delivered (e.g. `GtkWidget::key-press-event`) and finally a generic `GtkWidget::event-after` signal.

###### GtkWidget::event-after

After the emission of the `GtkWidget::event` signal and (optionally) the second more specific signal, ::event-after will be emitted regardless of the previous two signals handlers return values.

###### GtkWidget::focus

No description available.

###### GtkWidget::focus-in-event

The ::focus-in-event signal will be emitted when the keyboard focus enters the `widget`‘s window.

###### GtkWidget::focus-out-event

The ::focus-out-event signal will be emitted when the keyboard focus leaves the `widget`‘s window.

###### GtkWidget::grab-broken-event

Emitted when a pointer or keyboard grab on a window belonging to `widget` gets broken.

###### GtkWidget::grab-focus

No description available.

###### GtkWidget::grab-notify

The ::grab-notify signal is emitted when a widget becomes shadowed by a GTK+ grab (not a pointer or keyboard grab) on another widget, or when it becomes unshadowed due to a grab being removed.

###### GtkWidget::hide

The ::hide signal is emitted when `widget` is hidden, for example with gtk_widget_hide().

###### GtkWidget::hierarchy-changed

The ::hierarchy-changed signal is emitted when the anchored state of a widget changes. A widget is “anchored” when its toplevel ancestor is a `GtkWindow`. This signal is emitted when a widget changes from un-anchored to anchored or vice-versa.

###### GtkWidget::key-press-event

The ::key-press-event signal is emitted when a key is pressed. The signal emission will reoccur at the key-repeat rate when the key is kept pressed.

###### GtkWidget::key-release-event

The ::key-release-event signal is emitted when a key is released.

###### GtkWidget::keynav-failed

Gets emitted if keyboard navigation fails. See `gtk_widget_keynav_failed()` for details.

###### GtkWidget::leave-notify-event

The ::leave-notify-event will be emitted when the pointer leaves the `widget`‘s window.

###### GtkWidget::map

The ::map signal is emitted when `widget` is going to be mapped, that is when the widget is visible (which is controlled with gtk_widget_set_visible()) and all its parents up to the toplevel widget are also visible. Once the map has occurred, `GtkWidget::map-event` will be emitted.

###### GtkWidget::map-event

The ::map-event signal will be emitted when the `widget`‘s window is mapped. A window is mapped when it becomes visible on the screen.

###### GtkWidget::mnemonic-activate

The default handler for this signal activates `widget` if `group_cycling` is `FALSE`, or just makes `widget` grab focus if `group_cycling` is `TRUE`.

###### GtkWidget::motion-notify-event

The ::motion-notify-event signal is emitted when the pointer moves over the widget’s `GdkWindow`.

###### GtkWidget::move-focus

No description available.

###### GtkWidget::parent-set

The ::parent-set signal is emitted when a new parent has been set on a widget.

###### GtkWidget::popup-menu

This signal gets emitted whenever a widget should pop up a context menu. This usually happens through the standard key binding mechanism; by pressing a certain key while a widget is focused, the user can cause the widget to pop up a menu. For example, the `GtkEntry` widget creates a menu with clipboard commands. See the [Popup Menu Migration Checklist][checklist-popup-menu] for an example of how to use this signal.

###### GtkWidget::property-notify-event

The ::property-notify-event signal will be emitted when a property on the `widget`‘s window has been changed or deleted.

###### GtkWidget::proximity-in-event

To receive this signal the `GdkWindow` associated to the widget needs to enable the #GDK_PROXIMITY_IN_MASK mask.

###### GtkWidget::proximity-out-event

To receive this signal the `GdkWindow` associated to the widget needs to enable the #GDK_PROXIMITY_OUT_MASK mask.

###### GtkWidget::query-tooltip

Emitted when `GtkWidget:has-tooltip` is `TRUE` and the hover timeout has expired with the cursor hovering “above” `widget`; or emitted when `widget` got focus in keyboard mode.

###### GtkWidget::realize

The ::realize signal is emitted when `widget` is associated with a `GdkWindow`, which means that `gtk_widget_realize()` has been called or the widget has been mapped (that is, it is going to be drawn).

###### GtkWidget::screen-changed

The ::screen-changed signal gets emitted when the screen of a widget has changed.

###### GtkWidget::scroll-event

The ::scroll-event signal is emitted when a button in the 4 to 7 range is pressed. Wheel mice are usually configured to generate button press events for buttons 4 and 5 when the wheel is turned.

###### GtkWidget::selection-clear-event

The ::selection-clear-event signal will be emitted when the the `widget`‘s window has lost ownership of a selection.

###### GtkWidget::selection-get

No description available.

###### GtkWidget::selection-notify-event

No description available.

###### GtkWidget::selection-received

No description available.

###### GtkWidget::selection-request-event

The ::selection-request-event signal will be emitted when another client requests ownership of the selection owned by the `widget`‘s window.

###### GtkWidget::show

The ::show signal is emitted when `widget` is shown, for example with gtk_widget_show().

###### GtkWidget::show-help

No description available.

###### GtkWidget::size-allocate

No description available.

###### GtkWidget::state-changed

The ::state-changed signal is emitted when the widget state changes. See gtk_widget_get_state().

###### GtkWidget::state-flags-changed

The ::state-flags-changed signal is emitted when the widget state changes, see gtk_widget_get_state_flags().

###### GtkWidget::style-set

The ::style-set signal is emitted when a new style has been set on a widget. Note that style-modifying functions like `gtk_widget_modify_base()` also cause this signal to be emitted.

###### GtkWidget::style-updated

The ::style-updated signal is a convenience signal that is emitted when the `GtkStyleContext::changed` signal is emitted on the `widget`‘s associated `GtkStyleContext` as returned by gtk_widget_get_style_context().

###### GtkWidget::touch-event

No description available.

###### GtkWidget::unmap

The ::unmap signal is emitted when `widget` is going to be unmapped, which means that either it or any of its parents up to the toplevel widget have been set as hidden.

###### GtkWidget::unmap-event

The ::unmap-event signal will be emitted when the `widget`‘s window is unmapped. A window is unmapped when it becomes invisible on the screen.

###### GtkWidget::unrealize

The ::unrealize signal is emitted when the `GdkWindow` associated with `widget` is destroyed, which means that `gtk_widget_unrealize()` has been called or the widget has been unmapped (that is, it is going to be hidden).

###### GtkWidget::visibility-notify-event

The ::visibility-notify-event will be emitted when the `widget`‘s window is obscured or unobscured.

###### GtkWidget::window-state-event

The ::window-state-event will be emitted when the state of the toplevel window associated to the `widget` changes.

##### Signals inherited from GObject (1)

###### GObject::notify

The 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.

#### Class structure

    struct DevhelpAssistantViewClass {
      WebKitWebViewClass parent_class;
      gpointer padding;

    }

No description available.

###### Class members

`parent_class: WebKitWebViewClass`

  No description available.

`padding: gpointer`

  No description available.