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/Libraries/LibWeb/Layout/Label.h

45 lines
1.4 KiB
C
Raw Normal View History

LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
/*
Everywhere: Update copyrights with my new serenityos.org e-mail :^)
2022-01-31 13:07:22 -05:00
* Copyright (c) 2021, Tim Flynn <trflynn89@serenityos.org>
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
*
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 "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
*/
#pragma once
LibWeb: Enable EXPLICIT_SYMBOL_EXPORT
2025-07-19 19:35:33 -07:00
#include <LibWeb/Export.h>
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
#include <LibWeb/HTML/HTMLLabelElement.h>
LibWeb: Rename Layout::BlockBox => BlockContainer There's a subtle difference here. A "block box" in the spec is a block-level box, while a "block container" is a box whose children are either all inline-level boxes in an IFC, or all block-level boxes participating in a BFC. Notably, an "inline-block" box is a "block container" but not a "block box" since it is itself inline-level.
2021-10-06 20:02:41 +02:00
#include <LibWeb/Layout/BlockContainer.h>
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
namespace Web::Layout {
LibWeb: Enable EXPLICIT_SYMBOL_EXPORT
2025-07-19 19:35:33 -07:00
class WEB_API Label final : public BlockContainer {
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC_CELL(Label, BlockContainer);
GC_DECLARE_ALLOCATOR(Label);
LibWeb: Make the layout tree GC-allocated This removes a set of complex reference cycles between DOM, layout tree and browsing context. It also makes lifetimes much easier to reason about, as the DOM and layout trees are now free to keep each other alive.
2022-10-17 14:41:50 +02:00
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
public:
LibWeb: Make CSS::ComputedProperties GC-allocated
2024-12-20 16:35:12 +01:00
Label(DOM::Document&, HTML::HTMLLabelElement*, GC::Ref<CSS::ComputedProperties>);
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
virtual ~Label() override;
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
static bool is_inside_associated_label(LabelableNode const&, CSSPixelPoint);
LibWeb: Move mouse event and label logic from layout to painting tree Input events have nothing to do with layout, so let's not send them to layout nodes. The job of Paintable starts to become clear. It represents a paintable item that can be rendered into the viewport, which means it can also be targeted by the mouse cursor.
2022-03-10 22:46:35 +01:00
static bool is_associated_label_hovered(LabelableNode const&);
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
Everywhere: Change west consts caught by clang-format-21 to east consts
2025-08-29 13:02:52 +01:00
HTML::HTMLLabelElement const& dom_node() const { return static_cast<HTML::HTMLLabelElement const&>(*BlockContainer::dom_node()); }
LibWeb: Rename Layout::BlockBox => BlockContainer There's a subtle difference here. A "block box" in the spec is a block-level box, while a "block container" is a box whose children are either all inline-level boxes in an IFC, or all block-level boxes participating in a BFC. Notably, an "inline-block" box is a "block container" but not a "block box" since it is itself inline-level.
2021-10-06 20:02:41 +02:00
HTML::HTMLLabelElement& dom_node() { return static_cast<HTML::HTMLLabelElement&>(*BlockContainer::dom_node()); }
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
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
void handle_mousedown_on_label(Badge<Painting::TextPaintable>, CSSPixelPoint, unsigned button);
void handle_mouseup_on_label(Badge<Painting::TextPaintable>, CSSPixelPoint, unsigned button);
void handle_mousemove_on_label(Badge<Painting::TextPaintable>, CSSPixelPoint, unsigned button);
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
LibWeb: Defer mouse events from TextNode to Label A label's format is: <label>Label text</label> So, a TextNode is created as a child of the Label node, and EventHandler will send events to the TextNode. This changes TextNode to accept mouse events if its parent is a Label, and to forward those events upward.
2021-04-03 21:48:05 -04:00
private:
LibWeb: Add fast_is<T>() for Layout::Label Spotted this in a profile while wheel scrolling up & down.
2021-10-27 17:58:19 +02:00
virtual bool is_label() const override { return true; }
LibWeb: Move mouse event and label logic from layout to painting tree Input events have nothing to do with layout, so let's not send them to layout nodes. The job of Paintable starts to become clear. It represents a paintable item that can be rendered into the viewport, which means it can also be targeted by the mouse cursor.
2022-03-10 22:46:35 +01:00
static Label const* label_for_control_node(LabelableNode const&);
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
bool m_tracking_mouse { false };
};
LibWeb: Add fast_is<T>() for Layout::Label Spotted this in a profile while wheel scrolling up & down.
2021-10-27 17:58:19 +02:00
template<>
inline bool Node::fast_is<Label>() const { return is_label(); }
LibWeb: Add "Label" to be the layout node for HTMLLabelElement The HTML <label> element is special in that it may be associated with some other <input> element. When the label element is clicked, the input element should be activated. To achieve this, a LableableNode base class is introduced to provide an interface for "labelable" elements to handle mouse events on their associated labels. This not only allows clicking the label to activate the input, but dragging the mouse from the label to the input (and vice- versa) while the mouse is clicked will also active the label. As of this commit, this infrastructure is not hooked up to any elements.
2021-04-03 21:32:16 -04:00
}
Reference in a new issue Copy permalink