Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-19 15:43:20 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Userland/Libraries/LibWeb/Page/EventHandler.h

85 lines
3.1 KiB
C
Raw Normal View History

LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
/*
* Copyright (c) 2020, Andreas Kling <kling@serenityos.org>
*
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-04-22 01:24:48 -07:00
* SPDX-License-Identifier: BSD-2-Clause
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
*/
#pragma once
#include <AK/Forward.h>
Libraries: Add missing headers A C++ source file containing just #include <LibFoo/Bar.h> should always compile cleanly. This patch adds missing header inclusions that could have caused weird error messages if they were used in a different context. Also, this confused QtCreator.
2021-01-21 20:55:37 +01:00
#include <AK/NonnullOwnPtr.h>
LibWeb: Allow layout nodes to receive and track mouse events To implement form controls internally in LibWeb (necessary for multi process forms), we'll need the ability to handle events since we can't rely on LibGUI widgets anymore. A LayoutNode can now override wants_mouse_events() and if it returns true, it will now receive mousedown, mousemove and mouseup events. :^)
2020-09-11 18:15:47 +02:00
#include <AK/WeakPtr.h>
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
#include <LibGfx/Forward.h>
LibWeb: Use paintable to represent event tracking node The use of layout nodes likely predated the paintable tree, but now there is no point in introducing another level of indirection.
2024-01-14 10:14:36 +01:00
#include <LibJS/Heap/Cell.h>
LibWeb: Clear the mouse event tracking node when it stops wanting events This can occur if a mouse click on a mouse event tracking node causes a page navigation. As the old document is torn down, the event handler may have a stale reference to the tracking node. If a subsequent mouse event occurs on that node, we would crash trying to access the node's styled properties that are no longer valid. To fix this, when we are deciding what node to send the event to, and we have a mouse event tracking node, check if that node still wants the event. If not, clear the tracking node.
2023-04-27 09:19:20 -04:00
#include <LibJS/Heap/GCPtr.h>
LibWeb: Use a Unicode text segmenter to select words on double-click We currently use a naive word segmentation, looking for ASCII spaces to mark a word boundary. Use LibUnicode's complete implementation instead.
2024-08-27 08:19:03 -04:00
#include <LibUnicode/Forward.h>
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
#include <LibWeb/Forward.h>
LibWeb: Begin implementing the drag-and-drop processing model The drag-and-drop processing model allows for users to drag around either elements within the DOM or objects completely outside the DOM. This drag event can either end without action (via cancellation or user input), or in a drop event, where the dragged object is dropped onto another element within the DOM. The processing model is rather large. This implements enough of it to allow the UI process to specifically handle dragging objects outside of the DOM onto the DOM. For example, dragging an image from the OS file manager onto a file-upload input element. This does not implement the ability to drag DOM elements.
2024-08-17 13:29:55 -04:00
#include <LibWeb/Page/InputEvent.h>
LibWeb+WebContent+headless-browser: Use CSSPixels for PageClient events ...and also for hit testing, which is involved in most of them. Much of this is temporary conversions and other awkwardness, which should resolve itself as the rest of LibWeb is converted to these new types. Hopefully. :thousandyakstare:
2022-11-02 17:35:53 +00:00
#include <LibWeb/PixelUnits.h>
LibWeb: Add Web::UIEvents::KeyCode and KeyModifier enums, drop Kernel This was the last Kernel header we had. Move the definitions we need into a UIEvents header similar to MouseButton.
2024-06-06 13:29:08 -06:00
#include <LibWeb/UIEvents/KeyCode.h>
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
namespace Web {
class EventHandler {
public:
LibWeb: Move event handling & cursor from BrowsingContext to Navigable This was a long standing FIXME since the introduction of navigables.
2024-04-26 16:59:04 +02:00
explicit EventHandler(Badge<HTML::Navigable>, HTML::Navigable&);
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
~EventHandler();
Ladybird+LibWeb: Add MouseEvent screenX and screenY support
2023-09-08 18:48:44 +02:00
bool handle_mouseup(CSSPixelPoint, CSSPixelPoint screen_position, unsigned button, unsigned buttons, unsigned modifiers);
bool handle_mousedown(CSSPixelPoint, CSSPixelPoint screen_position, unsigned button, unsigned buttons, unsigned modifiers);
bool handle_mousemove(CSSPixelPoint, CSSPixelPoint screen_position, unsigned buttons, unsigned modifiers);
bool handle_mousewheel(CSSPixelPoint, CSSPixelPoint screen_position, unsigned button, unsigned buttons, unsigned modifiers, int wheel_delta_x, int wheel_delta_y);
bool handle_doubleclick(CSSPixelPoint, CSSPixelPoint screen_position, unsigned button, unsigned buttons, unsigned modifiers);
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
LibWeb: Begin implementing the drag-and-drop processing model The drag-and-drop processing model allows for users to drag around either elements within the DOM or objects completely outside the DOM. This drag event can either end without action (via cancellation or user input), or in a drop event, where the dragged object is dropped onto another element within the DOM. The processing model is rather large. This implements enough of it to allow the UI process to specifically handle dragging objects outside of the DOM onto the DOM. For example, dragging an image from the OS file manager onto a file-upload input element. This does not implement the ability to drag DOM elements.
2024-08-17 13:29:55 -04:00
bool handle_drag_and_drop_event(DragEvent::Type, CSSPixelPoint, CSSPixelPoint screen_position, unsigned button, unsigned buttons, unsigned modifiers, Vector<HTML::SelectedFile> files);
LibWeb: Add Web::UIEvents::KeyCode and KeyModifier enums, drop Kernel This was the last Kernel header we had. Move the definitions we need into a UIEvents header similar to MouseButton.
2024-06-06 13:29:08 -06:00
bool handle_keydown(UIEvents::KeyCode, unsigned modifiers, u32 code_point);
bool handle_keyup(UIEvents::KeyCode, unsigned modifiers, u32 code_point);
LibWeb: Allow inserting text at the cursor by typing characters :^) This works everywhere right now, but it's obviously not going to stay that way forever. :^) Note that this does not advance the cursor correctly for whitespace since the cursor is DOM-based and doesn't take whitespace collapsing into account yet.
2020-08-02 12:10:01 +02:00
LibWeb: Use paintable to represent event tracking node The use of layout nodes likely predated the paintable tree, but now there is no point in introducing another level of indirection.
2024-01-14 10:14:36 +01:00
void set_mouse_event_tracking_paintable(Painting::Paintable*);
LibWeb: Allow layout nodes to receive and track mouse events To implement form controls internally in LibWeb (necessary for multi process forms), we'll need the ability to handle events since we can't rely on LibGUI widgets anymore. A LayoutNode can now override wants_mouse_events() and if it returns true, it will now receive mousedown, mousemove and mouseup events. :^)
2020-09-11 18:15:47 +02:00
LibWeb+WebContent+Ladybird: Add ability to paste text from clipboard Text can be pasted by pressing Ctrl/Cmd+V or by using button in the context menu. For now only the Qt client is supported.
2024-03-22 11:56:49 +01:00
void handle_paste(String const& text);
LibWeb: Use paintable to represent event tracking node The use of layout nodes likely predated the paintable tree, but now there is no point in introducing another level of indirection.
2024-01-14 10:14:36 +01:00
void visit_edges(JS::Cell::Visitor& visitor) const;
LibWeb: Use a Unicode text segmenter to select words on double-click We currently use a naive word segmentation, looking for ASCII spaces to mark a word boundary. Use LibUnicode's complete implementation instead.
2024-08-27 08:19:03 -04:00
Unicode::Segmenter& word_segmenter();
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
private:
LibWeb: Allow focusing individual (focusable) elements with Tab key You can now cycle through focusable elements (currently only hyperlinks are focusable) with the Tab key. The focus outline is rendered in a new FocusOutline paint phase.
2020-08-14 19:40:37 +02:00
bool focus_next_element();
bool focus_previous_element();
LibWeb: Add Web::UIEvents::KeyCode and KeyModifier enums, drop Kernel This was the last Kernel header we had. Move the definitions we need into a UIEvents header similar to MouseButton.
2024-06-06 13:29:08 -06:00
bool fire_keyboard_event(FlyString const& event_name, HTML::Navigable&, UIEvents::KeyCode, unsigned modifiers, u32 code_point);
LibWeb: Fix calculation of MouseEvent::client_{x,y} MouseEvent.client{X,Y} should be relative to the viewport.
2022-12-31 16:04:48 +02:00
CSSPixelPoint compute_mouse_event_client_offset(CSSPixelPoint event_page_position) const;
LibWeb: Support MouseEvent.{pageX,pageY} Unlike client{X,Y} which is relative to the current viewport, these offsets are relative to the left edge of the document (i.e they take scroll offset into account).
2022-12-31 16:40:36 +02:00
CSSPixelPoint compute_mouse_event_page_offset(CSSPixelPoint event_client_offset) const;
LibWeb: Partially implement MouseEvent.movementX/movementY Currently doesn't handle the mouse leaving and entering the window per the spec, and uses clientX/Y instead of screenX/Y. See FIXMEs.
2023-08-24 17:47:13 +02:00
CSSPixelPoint compute_mouse_event_movement(CSSPixelPoint event_client_offset) const;
LibWeb: Make keyboard events properly fire into a focused iframe Google Docs focuses a "text event target" iframe using Window.focus on the iframe's contentWindow. Doing so makes the iframe's document the focused element we have to fire text events at. However, in the top level browsing context, the focused element is still the iframe, so we have to repeat the keyboard event steps but with the iframe's nested browsing context instead.
2022-11-05 15:36:03 +00:00
LibWeb: Clear the mouse event tracking node when it stops wanting events This can occur if a mouse click on a mouse event tracking node causes a page navigation. As the old document is torn down, the event handler may have a stale reference to the tracking node. If a subsequent mouse event occurs on that node, we would crash trying to access the node's styled properties that are no longer valid. To fix this, when we are deciding what node to send the event to, and we have a mouse event tracking node, check if that node still wants the event. If not, clear the tracking node.
2023-04-27 09:19:20 -04:00
struct Target {
JS::GCPtr<Painting::Paintable> paintable;
Optional<int> index_in_node;
};
Optional<Target> target_for_mouse_position(CSSPixelPoint position);
LibWeb: Move hit testing to the painting tree
2022-03-11 00:03:28 +01:00
Painting::PaintableBox* paint_root();
Painting::PaintableBox const* paint_root() const;
LibWeb: Begin implementing the drag-and-drop processing model The drag-and-drop processing model allows for users to drag around either elements within the DOM or objects completely outside the DOM. This drag event can either end without action (via cancellation or user input), or in a drop event, where the dragged object is dropped onto another element within the DOM. The processing model is rather large. This implements enough of it to allow the UI process to specifically handle dragging objects outside of the DOM onto the DOM. For example, dragging an image from the OS file manager onto a file-upload input element. This does not implement the ability to drag DOM elements.
2024-08-17 13:29:55 -04:00
bool should_ignore_device_input_event() const;
LibWeb: Update input/textarea selection on document selection change This causes UI interactions with the document selection to also update the input and textarea DOM selection state. Note that we switch around the order of focusing a DOM node and setting the selection, so we allow the focus event to override whatever selection we came up with.
2024-08-26 13:07:57 +02:00
void update_selection_range_for_input_or_textarea();
LibWeb: Begin implementing the drag-and-drop processing model The drag-and-drop processing model allows for users to drag around either elements within the DOM or objects completely outside the DOM. This drag event can either end without action (via cancellation or user input), or in a drop event, where the dragged object is dropped onto another element within the DOM. The processing model is rather large. This implements enough of it to allow the UI process to specifically handle dragging objects outside of the DOM onto the DOM. For example, dragging an image from the OS file manager onto a file-upload input element. This does not implement the ability to drag DOM elements.
2024-08-17 13:29:55 -04:00
LibWeb: Move event handling & cursor from BrowsingContext to Navigable This was a long standing FIXME since the introduction of navigables.
2024-04-26 16:59:04 +02:00
JS::NonnullGCPtr<HTML::Navigable> m_navigable;
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
bool m_in_mouse_selection { false };
LibWeb: Allow layout nodes to receive and track mouse events To implement form controls internally in LibWeb (necessary for multi process forms), we'll need the ability to handle events since we can't rely on LibGUI widgets anymore. A LayoutNode can now override wants_mouse_events() and if it returns true, it will now receive mousedown, mousemove and mouseup events. :^)
2020-09-11 18:15:47 +02:00
LibWeb: Use paintable to represent event tracking node The use of layout nodes likely predated the paintable tree, but now there is no point in introducing another level of indirection.
2024-01-14 10:14:36 +01:00
JS::GCPtr<Painting::Paintable> m_mouse_event_tracking_paintable;
LibWeb: Move editing stuff into EditEventHandler.
2020-12-01 23:35:47 +01:00
NonnullOwnPtr<EditEventHandler> m_edit_event_handler;
LibWeb: Begin implementing the drag-and-drop processing model The drag-and-drop processing model allows for users to drag around either elements within the DOM or objects completely outside the DOM. This drag event can either end without action (via cancellation or user input), or in a drop event, where the dragged object is dropped onto another element within the DOM. The processing model is rather large. This implements enough of it to allow the UI process to specifically handle dragging objects outside of the DOM onto the DOM. For example, dragging an image from the OS file manager onto a file-upload input element. This does not implement the ability to drag DOM elements.
2024-08-17 13:29:55 -04:00
NonnullOwnPtr<DragAndDropEventHandler> m_drag_and_drop_event_handler;
LibWeb: Dispatch a click event after mousedown+mouseup on same target
2022-02-07 13:27:17 +01:00
WeakPtr<DOM::EventTarget> m_mousedown_target;
LibWeb: Partially implement MouseEvent.movementX/movementY Currently doesn't handle the mouse leaving and entering the window per the spec, and uses clientX/Y instead of screenX/Y. See FIXMEs.
2023-08-24 17:47:13 +02:00
Ladybird+LibWeb: Add MouseEvent screenX and screenY support
2023-09-08 18:48:44 +02:00
Optional<CSSPixelPoint> m_mousemove_previous_screen_position;
LibWeb: Use a Unicode text segmenter to select words on double-click We currently use a naive word segmentation, looking for ASCII spaces to mark a word boundary. Use LibUnicode's complete implementation instead.
2024-08-27 08:19:03 -04:00
OwnPtr<Unicode::Segmenter> m_word_segmenter;
LibWeb: Add per-Frame EventHandler, handle mouse events recursively We now handle mouse events by recursing into subframes. This makes links, tooltips, etc, work inside <iframe> content.
2020-06-07 14:40:38 +02:00
};
}
Reference in a new issue Copy permalink