Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-31 13:20:59 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Libraries/LibWeb/HTML/HTMLTextAreaElement.h

168 lines
6.1 KiB
C
Raw Normal View History

LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01:00
/*
Everywhere: Use "the SerenityOS developers." in copyright headers We had some inconsistencies before: - Sometimes "The", sometimes "the" - Sometimes trailing ".", sometimes no trailing "." I picked the most common one (lowecase "the", trailing ".") and applied it to all copyright headers. By using the exact same string everywhere we can ensure nothing gets missed during a global search (and replace), and that these inconsistencies are not spread any further (as copyright headers are commonly copied to new files).
2021-04-28 22:46:44 +02:00
* Copyright (c) 2020, the SerenityOS developers.
LibWeb: Add form associated element categories
2022-03-01 21:03:30 +00:00
* Copyright (c) 2022, Luke Wilde <lukew@serenityos.org>
LibWeb: Add input and textarea minlength and maxlength support
2024-03-01 08:49:04 +01:00
* Copyright (c) 2024, Bastiaan van der Plaat <bastiaan.v.d.plaat@gmail.com>
Meta: Update my email address everywhere
2024-11-01 12:14:53 +01:00
* Copyright (c) 2024, Jelle Raaijmakers <jelle@ladybird.org>
LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01: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 all HTML elements between S and V
2020-08-01 03:07:00 +01:00
*/
#pragma once
LibWeb: Capture weak `this` ptr in HTMLTextAreaElement input callback Fixes GC-leak caused by cycle dependency between input callback and HTMLTextAreaElement that owns it.
2024-03-16 11:44:18 +01:00
#include <LibCore/Timer.h>
LibWeb: Move ARIA-related code into the Web::ARIA namespace ARIA has its own spec and is not part of the DOM spec, which is what the Web::DOM namespace is for (https://www.w3.org/TR/wai-aria-1.2/). This allows us to stay closer to the spec with function names and don't have to add the word "ARIA" to identifiers constantly - the namespace now provides that clarity.
2023-01-28 22:23:16 +00:00
#include <LibWeb/ARIA/Roles.h>
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
#include <LibWeb/DOM/Text.h>
LibWeb: Make FormAssociatedElement inherit from HTMLElement The new event target implementation requires us to downcast an EventTarget to a FormAssociatedElement to check if the current Element EventTarget has a form owner to setup a with scope for the form owner. This also makes all form associated elements inherit from FormAssociatedElement where it was previously missing. https://html.spec.whatwg.org/#form-associated-element
2021-10-14 16:18:49 +01:00
#include <LibWeb/HTML/FormAssociatedElement.h>
LibWeb: Remove inheritance of FormAssociatedElement from HTMLElement HTMLObjectElement will need to be both a FormAssociatedElement and a BrowsingContextContainer. Currently, both of these classes inherit from HTMLElement. This can work in C++, but is generally frowned upon, and doesn't play particularly well with the rest of LibWeb. Instead, we can essentially revert commit 3bb5c62 to remove HTMLElement from FormAssociatedElement's hierarchy. This means that objects such as HTMLObjectElement individually inherit from FormAssociatedElement and HTMLElement now. Some caveats are: * FormAssociatedElement still needs to know when the HTMLElement is inserted into and removed from the DOM. This hook is automatically injected via a macro now, while still allowing classes like HTMLInputElement to also know when the element is inserted. * Casting from a DOM::Element to a FormAssociatedElement is now a sideways cast, rather than directly following an inheritance chain. This means static_cast cannot be used here; but we can safely use dynamic_cast since the only 2 instances of this already use RTTI to verify the cast.
2022-03-23 18:55:54 -04:00
#include <LibWeb/HTML/HTMLElement.h>
LibWeb: Add input and textarea minlength and maxlength support
2024-03-01 08:49:04 +01:00
#include <LibWeb/WebIDL/Types.h>
LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01:00
namespace Web::HTML {
LibWeb: Remove inheritance of FormAssociatedElement from HTMLElement HTMLObjectElement will need to be both a FormAssociatedElement and a BrowsingContextContainer. Currently, both of these classes inherit from HTMLElement. This can work in C++, but is generally frowned upon, and doesn't play particularly well with the rest of LibWeb. Instead, we can essentially revert commit 3bb5c62 to remove HTMLElement from FormAssociatedElement's hierarchy. This means that objects such as HTMLObjectElement individually inherit from FormAssociatedElement and HTMLElement now. Some caveats are: * FormAssociatedElement still needs to know when the HTMLElement is inserted into and removed from the DOM. This hook is automatically injected via a macro now, while still allowing classes like HTMLInputElement to also know when the element is inserted. * Casting from a DOM::Element to a FormAssociatedElement is now a sideways cast, rather than directly following an inheritance chain. This means static_cast cannot be used here; but we can safely use dynamic_cast since the only 2 instances of this already use RTTI to verify the cast.
2022-03-23 18:55:54 -04:00
class HTMLTextAreaElement final
: public HTMLElement
LibWeb: Delete EditableTextNodeOwner It's no longer needed after FormAssociatedTextControlElement became responsible for managing input events for text controls.
2024-11-06 16:46:50 +01:00
, public FormAssociatedTextControlElement {
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
WEB_PLATFORM_OBJECT(HTMLTextAreaElement, HTMLElement);
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_DECLARE_ALLOCATOR(HTMLTextAreaElement);
LibWeb: Remove inheritance of FormAssociatedElement from HTMLElement HTMLObjectElement will need to be both a FormAssociatedElement and a BrowsingContextContainer. Currently, both of these classes inherit from HTMLElement. This can work in C++, but is generally frowned upon, and doesn't play particularly well with the rest of LibWeb. Instead, we can essentially revert commit 3bb5c62 to remove HTMLElement from FormAssociatedElement's hierarchy. This means that objects such as HTMLObjectElement individually inherit from FormAssociatedElement and HTMLElement now. Some caveats are: * FormAssociatedElement still needs to know when the HTMLElement is inserted into and removed from the DOM. This hook is automatically injected via a macro now, while still allowing classes like HTMLInputElement to also know when the element is inserted. * Casting from a DOM::Element to a FormAssociatedElement is now a sideways cast, rather than directly following an inheritance chain. This means static_cast cannot be used here; but we can safely use dynamic_cast since the only 2 instances of this already use RTTI to verify the cast.
2022-03-23 18:55:54 -04:00
FORM_ASSOCIATED_ELEMENT(HTMLElement, HTMLTextAreaElement)
LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01:00
public:
virtual ~HTMLTextAreaElement() override;
LibWeb: Rename CSS::StyleProperties => CSS::ComputedProperties Now that StyleProperties is only used to hold computed properties, let's name it ComputedProperties.
2024-12-20 11:32:17 +01:00
virtual void adjust_computed_style(CSS::ComputedProperties&) override;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
LibWeb: Port HTMLTextAreaElement from DeprecatedString
2023-11-26 10:59:52 +13:00
String const& type() const
Meta+LibHTTP through LibWeb: Make clang-format-10 clean
2020-09-18 09:49:51 +02:00
{
LibWeb: Port HTMLTextAreaElement from DeprecatedString
2023-11-26 10:59:52 +13:00
static String const textarea = "textarea"_string;
LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01:00
return textarea;
}
LibWeb: Add form associated element categories
2022-03-01 21:03:30 +00:00
LibWeb: Make HTML{Button,Select,TextArea}Element focusable From the HTML spec: Modulo platform conventions, it is suggested that the following elements should be considered as focusable areas and be sequentially focusable: ... - button elements - select elements - textarea elements ... Also add a spec link to the existing HTMLAnchorElement::is_focusable(). Note that this still doesn't allow triggering keyboard-focused buttons, checkboxes, or radio buttons - we don't seem to run the expected activation behavior for any of them.
2022-03-26 18:05:48 +00:00
// ^EventTarget
// https://html.spec.whatwg.org/multipage/interaction.html#the-tabindex-attribute:the-textarea-element
LibWeb: Do not allow focusing "Actually Disabled" elements
2024-11-02 19:17:20 +01:00
// https://html.spec.whatwg.org/multipage/interaction.html#focusable-area
// https://html.spec.whatwg.org/multipage/semantics-other.html#concept-element-disabled
virtual bool is_focusable() const override;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
virtual void did_lose_focus() override;
virtual void did_receive_focus() override;
LibWeb: Make HTML{Button,Select,TextArea}Element focusable From the HTML spec: Modulo platform conventions, it is suggested that the following elements should be considered as focusable areas and be sequentially focusable: ... - button elements - select elements - textarea elements ... Also add a spec link to the existing HTMLAnchorElement::is_focusable(). Note that this still doesn't allow triggering keyboard-focused buttons, checkboxes, or radio buttons - we don't seem to run the expected activation behavior for any of them.
2022-03-26 18:05:48 +00:00
LibWeb: Add form associated element categories
2022-03-01 21:03:30 +00:00
// ^FormAssociatedElement
// https://html.spec.whatwg.org/multipage/forms.html#category-listed
virtual bool is_listed() const override { return true; }
// https://html.spec.whatwg.org/multipage/forms.html#category-submit
virtual bool is_submittable() const override { return true; }
// https://html.spec.whatwg.org/multipage/forms.html#category-reset
virtual bool is_resettable() const override { return true; }
// https://html.spec.whatwg.org/multipage/forms.html#category-autocapitalize
virtual bool is_auto_capitalize_inheriting() const override { return true; }
// https://html.spec.whatwg.org/multipage/forms.html#category-label
virtual bool is_labelable() const override { return true; }
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
LibWeb: Add stub reset algorithm for HTMLTextAreaElement
2022-12-22 19:58:21 -05:00
virtual void reset_algorithm() override;
LibWeb: Implement the form associated element clear algorithm This is a method defined in the WebDriver spec, but requires access to a bunch of private fields in these classes, so this is implemented in the same manner as the reset algorithm.
2024-10-11 10:38:43 -04:00
virtual void clear_algorithm() override;
LibWeb: Add stub reset algorithm for HTMLTextAreaElement
2022-12-22 19:58:21 -05:00
LibWeb: Make node cloning methods const
2025-01-11 17:37:08 +00:00
virtual WebIDL::ExceptionOr<void> cloned(Node&, bool) const override;
LibWeb: Implement cloning steps for `HTMLTextAreaElement`
2024-08-21 12:27:30 +01:00
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
virtual void form_associated_element_was_inserted() override;
LibWeb: Remove shadow roots from elements that are removed from the DOM We currently create a shadow tree once for each DOM element that renders with a shadow tree (e.g. <input>, <details>). If such an element is removed from the DOM, we must remove its shadow tree. Otherwise, the shadow tree will refer to the old document in perpetuity. If the node is added back to a DOM, then recreate the shadow tree.
2023-11-29 18:22:16 -05:00
virtual void form_associated_element_was_removed(DOM::Node*) override;
LibWeb: Include namespace parameter in `associated_attribute_changed()`
2024-12-12 19:48:32 +00:00
virtual void form_associated_element_attribute_changed(FlyString const&, Optional<String> const&, Optional<FlyString> const&) override;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
virtual void children_changed() override;
LibWeb: Add Support for the ARIA Element Properties Element now supports getting and setting ARIA properties from JS and HTML.
2022-11-28 17:58:13 -06:00
// https://www.w3.org/TR/html-aria/#el-textarea
LibWeb: Move ARIA-related code into the Web::ARIA namespace ARIA has its own spec and is not part of the DOM spec, which is what the Web::DOM namespace is for (https://www.w3.org/TR/wai-aria-1.2/). This allows us to stay closer to the spec with function names and don't have to add the word "ARIA" to identifiers constantly - the namespace now provides that clarity.
2023-01-28 22:23:16 +00:00
virtual Optional<ARIA::Role> default_role() const override { return ARIA::Role::textbox; }
LibWeb: Add Support for the ARIA Element Properties Element now supports getting and setting ARIA properties from JS and HTML.
2022-11-28 17:58:13 -06:00
LibWeb: Add textarea value properties
2023-12-10 17:48:42 +01:00
String default_value() const;
void set_default_value(String const&);
String value() const override;
void set_value(String const&);
LibWeb: Implement input/textarea selection APIs For both types of elements, `.selectionStart`, `.selectionEnd`, `.selectionDirection`, `.setSelectionRange()`, `.select()` and the `select` event are now implemented.
2024-08-22 15:20:24 +02:00
// https://html.spec.whatwg.org/multipage/form-elements.html#the-textarea-element:concept-fe-api-value-3
String api_value() const;
LibWeb: Subclass FormAssociatedElement text selection methods These are only relevant to HTMLInputElement and HTMLTextArea elements.
2024-08-30 17:22:58 +01:00
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#concept-textarea/input-relevant-value
virtual String relevant_value() override { return api_value(); }
LibWeb: Implement setRangeText for input and textarea elements This method replaces range of text in its respective element with a new string
2024-08-30 17:22:58 +01:00
virtual WebIDL::ExceptionOr<void> set_relevant_value(String const& value) override;
virtual void set_dirty_value_flag(bool flag) override { m_dirty_value = flag; }
LibWeb: Subclass FormAssociatedElement text selection methods These are only relevant to HTMLInputElement and HTMLTextArea elements.
2024-08-30 17:22:58 +01:00
LibWeb: Add textarea value properties
2023-12-10 17:48:42 +01:00
u32 text_length() const;
LibWeb: Stub out a few HTMLTextArea validity IDL methods These are invoked by GitHub when submitting a comment. Stub them out for now, as this is enough to let GitHub proceed with (attempting) to submit the comment.
2024-03-06 14:44:05 -05:00
bool check_validity();
bool report_validity();
void set_custom_validity(String const& error);
LibWeb: Add input and textarea minlength and maxlength support
2024-03-01 08:49:04 +01:00
WebIDL::Long max_length() const;
WebIDL::ExceptionOr<void> set_max_length(WebIDL::Long);
WebIDL::Long min_length() const;
WebIDL::ExceptionOr<void> set_min_length(WebIDL::Long);
LibWeb: Don't allow `HTMLTextAreaElement` rows and cols to be set to 0 In this case we should fall back to the default value.
2024-11-28 16:08:14 +00:00
WebIDL::UnsignedLong cols() const;
LibWeb: Add textarea value properties
2023-12-10 17:48:42 +01:00
WebIDL::ExceptionOr<void> set_cols(unsigned);
LibWeb: Add textarea cols and rows attribute
2023-11-24 17:39:38 +01:00
LibWeb: Don't allow `HTMLTextAreaElement` rows and cols to be set to 0 In this case we should fall back to the default value.
2024-11-28 16:08:14 +00:00
WebIDL::UnsignedLong rows() const;
WebIDL::ExceptionOr<void> set_rows(WebIDL::UnsignedLong);
LibWeb: Add textarea cols and rows attribute
2023-11-24 17:39:38 +01:00
LibWeb: Implement input/textarea selection APIs For both types of elements, `.selectionStart`, `.selectionEnd`, `.selectionDirection`, `.setSelectionRange()`, `.select()` and the `select` event are now implemented.
2024-08-22 15:20:24 +02:00
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#dom-textarea/input-selectionstart
WebIDL::UnsignedLong selection_start_binding() const;
WebIDL::ExceptionOr<void> set_selection_start_binding(WebIDL::UnsignedLong const&);
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#dom-textarea/input-selectionend
WebIDL::UnsignedLong selection_end_binding() const;
WebIDL::ExceptionOr<void> set_selection_end_binding(WebIDL::UnsignedLong const&);
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#dom-textarea/input-selectiondirection
String selection_direction_binding() const;
LibWeb: Follow spec steps to set the selectionDirection attribute value
2024-10-04 12:12:39 +01:00
void set_selection_direction_binding(String const& direction);
LibWeb: Implement input/textarea selection APIs For both types of elements, `.selectionStart`, `.selectionEnd`, `.selectionDirection`, `.setSelectionRange()`, `.select()` and the `select` event are now implemented.
2024-08-22 15:20:24 +02:00
LibWeb: Implement setRangeText for input and textarea elements This method replaces range of text in its respective element with a new string
2024-08-30 17:22:58 +01:00
void set_dirty_value_flag(Badge<FormAssociatedElement>, bool flag) { m_dirty_value = flag; }
LibWeb: Delete EditableTextNodeOwner It's no longer needed after FormAssociatedTextControlElement became responsible for managing input events for text controls.
2024-11-06 16:46:50 +01:00
// ^FormAssociatedTextControlElement
virtual void did_edit_text_node() override;
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
virtual GC::Ptr<DOM::Text> form_associated_element_to_text_node() override { return m_text_node; }
LibWeb: Propagate input/textarea selection update to document selection Calling `.setSelectionRange()` or `.select()` now updates the document selection as well, visualizing the text selection.
2024-08-26 14:08:40 +02:00
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
private:
HTMLTextAreaElement(DOM::Document&, DOM::QualifiedName);
LibWeb: Implement HTMLOrSVGElement.tabIndex
2022-11-05 03:58:14 +00:00
LibJS: Make Cell::initialize() return void Stop worrying about tiny OOMs. Work towards #20405
2023-08-07 08:41:28 +02:00
virtual void initialize(JS::Realm&) override;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
virtual void visit_edges(Cell::Visitor&) override;
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
LibWeb: Use the <textarea>'s API value, not its raw value, where needed The API value of a <textarea> element is its raw value with normalized newlines. This should be used in a couple of places where we currently use the raw value.
2024-03-14 07:26:26 -04:00
void set_raw_value(String);
LibWeb: Implement HTMLOrSVGElement.tabIndex
2022-11-05 03:58:14 +00:00
// ^DOM::Element
virtual i32 default_tab_index_value() const override;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
void create_shadow_tree_if_needed();
LibWeb: Add textarea readonly support
2024-02-26 19:12:32 +01:00
void handle_readonly_attribute(Optional<String> const& value);
LibWeb: Add input and textarea minlength and maxlength support
2024-03-01 08:49:04 +01:00
void handle_maxlength_attribute();
LibWeb: Add textarea readonly support
2024-02-26 19:12:32 +01:00
LibWeb: Update the stored textarea value upon change And fire the "input" event upon change. This is needed to submit a comment on GitHub; otherwise, GitHub thinks the textarea value is empty.
2024-03-06 15:14:20 -05:00
void queue_firing_input_event();
LibWeb: Add textarea placeholder
2023-12-21 18:13:16 +01:00
void update_placeholder_visibility();
LibWeb: Implement input/textarea selection APIs For both types of elements, `.selectionStart`, `.selectionEnd`, `.selectionDirection`, `.setSelectionRange()`, `.select()` and the `select` event are now implemented.
2024-08-22 15:20:24 +02:00
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::Ptr<DOM::Element> m_placeholder_element;
GC::Ptr<DOM::Text> m_placeholder_text_node;
LibWeb: Add textarea placeholder
2023-12-21 18:13:16 +01:00
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::Ptr<DOM::Element> m_inner_text_element;
GC::Ptr<DOM::Text> m_text_node;
LibWeb: Flesh out HTMLTextAreaElement Give it a shadow tree, similar to HTMLInputElement's, so that we can actually edit its contents at a basic level. Add some CSS to use the `rows` and `cols` attributes as the size if they are present.
2023-08-30 17:10:38 +01:00
LibWeb: Capture weak `this` ptr in HTMLTextAreaElement input callback Fixes GC-leak caused by cycle dependency between input callback and HTMLTextAreaElement that owns it.
2024-03-16 11:44:18 +01:00
RefPtr<Core::Timer> m_input_event_timer;
LibWeb: Update the stored textarea value upon change And fire the "input" event upon change. This is needed to submit a comment on GitHub; otherwise, GitHub thinks the textarea value is empty.
2024-03-06 15:14:20 -05:00
LibWeb: Add textarea readonly support
2024-02-26 19:12:32 +01:00
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#concept-fe-dirty
bool m_dirty_value { false };
// https://html.spec.whatwg.org/multipage/form-elements.html#concept-textarea-raw-value
LibWeb: Port HTMLTextAreaElement from DeprecatedString
2023-11-26 10:59:52 +13:00
String m_raw_value;
LibWeb: Use the <textarea>'s API value, not its raw value, where needed The API value of a <textarea> element is its raw value with normalized newlines. This should be used in a couple of places where we currently use the raw value.
2024-03-14 07:26:26 -04:00
// https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#concept-fe-api-value
mutable Optional<String> m_api_value;
LibWeb: Add all HTML elements between S and V
2020-08-01 03:07:00 +01:00
};
}
Reference in a new issue Copy permalink