dmaax/ladybird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ladybird/Libraries/LibWeb/DOM/Node.h

519 lines
21 KiB
C
Raw Normal View History

Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 05:38:21 -03:00
/*
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
* Copyright (c) 2018-2025, Andreas Kling <andreas@ladybird.org>
Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 05:38:21 -03: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 05:24:48 -03:00
* SPDX-License-Identifier: BSD-2-Clause
Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 05:38:21 -03:00
*/
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
#pragma once
LibWeb: Make DOM Node unique IDs strongly typed (and 64 bit) This is strictly nicer than passing them around as i32 everywhere, and by switching to i64 as the underlying type, ID allocation becomes as simple as incrementing an integer.
2024-10-20 05:37:44 -03:00
#include <AK/DistinctNumeric.h>
LibWeb: Port MutationRecord types to FlyString Co-authored-by: Luke Wilde <lukew@serenityos.org>
2023-03-18 11:59:48 -03:00
#include <AK/FlyString.h>
LibWeb: Calculate length for all `CharacterData` type nodes correctly We now ensure that `Node::is_character_data()` returns true for all nodes of type character data. Previously, calling `Node::length()` on `CDataSection` or `ProcessingInstruction` nodes would return an incorrect value.
2024-07-23 17:55:48 -03:00
#include <AK/GenericShorthands.h>
LibWeb: Add JSON serialization method to DOM::Node This method builds a JSON object representing the full state of the DOM tree. The JSON that is built will be used for building the DOM Inspector widget for the OutOfProcessWebView.
2021-06-07 12:32:24 -03:00
#include <AK/JsonObjectSerializer.h>
LibWeb: Switch to using AK::is and AK::downcast
2020-07-26 12:16:18 -03:00
#include <AK/TypeCasts.h>
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
#include <AK/Vector.h>
LibWeb: Use invalidation sets to reduce style recalculation Implements idea described in https://docs.google.com/document/d/1vEW86DaeVs4uQzNFI5R-_xS9TcS1Cs_EUsHRSgCHGu8 Invalidation sets are used to reduce the number of elements marked for style recalculation by collecting metadata from style rules about the dependencies between properties that could affect an element’s style. Currently, this optimization is only applied to style invalidation triggered by class list mutations on an element.
2025-01-12 12:38:05 -03:00
#include <LibWeb/CSS/InvalidationSet.h>
LibWeb: Add Functionality to Dump to Accessibility Tree This will be used to display the accessibility tree in the inspector.
2022-12-11 13:56:37 -03:00
#include <LibWeb/DOM/AccessibilityTreeNode.h>
LibWeb: Start working on DOM event support This patch adds the EventTarget class and makes Node inherit from it. You can register event listeners on an EventTarget, and when you call dispatch_event() on it, the event listeners will get invoked. An event listener is basically a wrapper around a JS::Function*. This is pretty far from how DOM events should eventually work, but it's a place to start and we'll build more on top of this. :^)
2020-03-18 11:22:31 -03:00
#include <LibWeb/DOM/EventTarget.h>
LibWeb: Move DOM::NodeType to its own file This is to allow using these values in libraries that otherwise do not need to depend on LibWeb.
2025-02-14 12:31:44 -03:00
#include <LibWeb/DOM/NodeType.h>
LibWeb: Introduce the slottable concept for DOM elements and text nodes A slottable is either a DOM element or a DOM text node. They may be assigned to slots (HTMLSlotElement) either automatically or manually. Automatic assignment occurs by matching a slot's `name` attribute to a slottable's `slot` attribute. Manual assignment occurs by using the slot's (not yet implemented) `assign` API. This commit does not perform the above assignments. It just sets up the slottable concept via IDL and hooks the slottable mixin into the element and text nodes.
2023-09-05 14:07:35 -03:00
#include <LibWeb/DOM/Slottable.h>
LibWeb: Enable EXPLICIT_SYMBOL_EXPORT
2025-07-19 23:35:33 -03:00
#include <LibWeb/Export.h>
LibWeb: Move XMLSerializer into HTML directory The DOMParsing spec is in the process of being merged into the HTML one, gradually. The linked spec change moves XMLSerializer, but many of the algorithms are still in the DOMParsing spec so I've left the links to those alone. I've done my best to update the GN build but since I'm not actually using it, I might have done that wrong. Corresponds to https://github.com/whatwg/html/commit/2edb8cc7eefc6b918c181ea470350d9447423819
2025-03-03 10:04:14 -03:00
#include <LibWeb/HTML/XMLSerializer.h>
LibWeb: Use `TraversalDecision` for multi level Node traversal methods This adds the `SkipChildrenAndContinue` option, where traversal continues but child nodes are not included.
2024-05-04 10:47:04 -03:00
#include <LibWeb/TraversalDecision.h>
LibWeb/DOM: Inherit Node from TreeNode This allows to delete lots of tree helper functions duplicated between Node and TreeNode.
2025-02-03 11:25:24 -03:00
#include <LibWeb/TreeNode.h>
LibWeb: Move ExceptionOr from DOM/ to WebIDL/ This is a concept fully defined in the Web IDL spec and doesn't belong in the DOM directory/namespace - not even DOMException, despite the name :^)
2022-09-25 13:03:42 -03:00
#include <LibWeb/WebIDL/ExceptionOr.h>
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
LibWeb: Move DOM classes into the Web::DOM namespace LibWeb keeps growing and the Web namespace is filling up fast. Let's put DOM stuff into Web::DOM, just like we already started doing with SVG stuff in Web::SVG.
2020-07-26 14:37:56 -03:00
namespace Web::DOM {
LibWeb: Move everything into the Web namespace
2020-03-07 06:27:02 -03:00
LibWeb: Implement Accessible Name and Description Calculation This is an initial implementation of the accname standard. There is still some of the algorithm left unimplemented that we will need to implement in the future. However, as is, this implementation is sufficient for basic pages.
2023-02-05 14:21:59 -03:00
enum class NameOrDescription {
Name,
Description
};
LibWeb: Implement Node.getRootNode
2021-10-15 23:04:55 -03:00
struct GetRootNodeOptions {
bool composed { false };
};
LibWeb: Implement Element.outerHTML This piggybacks on the same fragment serialization code that innerHTML uses, but instead of constructing an imaginary parent element like the spec asks us to, we just add a separate serialization mode that includes the context element in the serialized markup. This makes the image carousel on https://utah.edu/ show up :^)
2024-04-09 09:44:58 -03:00
enum class FragmentSerializationMode {
Inner,
Outer,
};
LibWeb: Correctly descend element nodes when computing accessible name This change implements the “is a descendant of a native host language text alternative element” condition in the “F: Name From Content” step at https://w3c.github.io/accname/#step2F in the “Accessible Name and Description Computation” spec — to ensure that all descendant nodes get included as expected in computations for accessible names for elements. Otherwise, without this change, Ladybird unexpectedly skips descendant element nodes when computing accessible names — which can result in the wrong accessible name being returned.
2024-11-01 09:11:32 -03:00
enum class IsDescendant {
No,
Yes,
};
LibWeb: Allow accessible-name computation to skip role-attribute lookup Per https://w3c.github.io/aria/#document-handling_author-errors_roles, determining whether to ignore certain specified landmark roles requires first determining whether the element for which the role is specified has an accessible name. But if we then try to retrieve a role for such elements, we end up calling right back into the accessible-name computation code — which would cause the calls to loop infinitely. So to avoid that — and to have handling for any other future cases the spec may introduce of such recursive calls that will loop indefinitely — this change introduces a parameter that callers can pass to cause role-attribute lookup to be skipped during accessible-name computation.
2024-12-19 11:21:48 -03:00
enum class ShouldComputeRole {
No,
Yes,
};
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
#define ENUMERATE_STYLE_INVALIDATION_REASONS(X) \
X(AdoptedStyleSheetsList) \
LibWeb: Update base URL change processing Corresponds to https://github.com/whatwg/html/commit/49f5cd381e2e918e161fed5bd950d24723e6db2d
2025-08-07 09:37:11 -03:00
X(BaseURLChanged) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(CSSFontLoaded) \
X(CSSImportRule) \
LibWeb: Invalidate owner sheet on add/remove in CSSStyleProperties Fixes at least 2 WPT subtests.
2025-04-24 09:25:50 -03:00
X(CSSStylePropertiesRemoveProperty) \
X(CSSStylePropertiesSetProperty) \
LibWeb: Invalidate sheet owners after mutating cssText of its rules This fixes one source of flakiness on WPT (of many) where we wouldn't recompute style after programmatically altering the contents of a style sheet, but instead had to wait for something else to cause invalidation.
2025-04-12 06:44:41 -03:00
X(CSSStylePropertiesTextChange) \
LibWeb: Add style invalidation for :defined selector
2024-11-06 11:49:22 -03:00
X(CustomElementStateChange) \
LibWeb: Add CustomStateSet IDL type
2025-07-03 13:32:10 -03:00
X(CustomStateSetChange) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(DidLoseFocus) \
X(DidReceiveFocus) \
X(EditingInsertion) \
LibWeb: Fire change events on deletion in FormAssociated Text Elements Previously we would only trigger change events on insertion, which resulted in javascript code missing changes due to deletion. This makes the calculator on the MDN simple web worker demo update on deletion as well.
2025-08-30 13:55:52 -03:00
X(EditingDeletion) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(ElementAttributeChange) \
X(ElementSetShadowRoot) \
LibWeb: Add missing StyleInvalidationReason for HTMLDialogElement We were accidentally using NodeRemove instead of a unique reason.
2025-08-18 18:20:20 -03:00
X(HTMLDialogElementSetIsModal) \
LibWeb: Add style invalidation for :target, :focus, :active and :link
2024-11-06 14:00:18 -03:00
X(HTMLHyperlinkElementHrefChange) \
LibWeb: Avoid many style invalidations on DOM attribute mutation Many times, attribute mutation doesn't necessitate a full style invalidation on the element. However, the conditions are pretty elaborate, so this first version has a lot of false positives. We only need to invalidate style when any of these things apply: 1. The change may affect the match state of a selector somewhere. 2. The change may affect presentational hints applied to the element. For (1) in this first version, we have a fixed list of attribute names that may affect selectors. We also collect all names referenced by attribute selectors anywhere in the document. For (2), we add a new Element::is_presentational_hint() virtual that tells us whether a given attribute name is a presentational hint. This drastically reduces style work on many websites. As an example, https://cnn.com/ is once again browseable.
2024-12-23 13:51:10 -03:00
X(HTMLIFrameElementGeometryChange) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(HTMLInputElementSetChecked) \
LibWeb: Support :open for file and color `<input>` elements
2025-01-31 12:34:34 -03:00
X(HTMLInputElementSetIsOpen) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(HTMLObjectElementUpdateLayoutAndChildObjects) \
LibWeb: Avoid invalidation on .textContent setter no-op When setting the textContent of an element with no children to null or the empty string, nothing happens. Even so, we were still invalidating style, layout and collections, causing pointless churn. Skipping invalidation in this case also revealed that we were missing invalidation when changing the selected state of HTMLOptionElement. This was all caught by existing tests already in-tree. :^)
2025-01-03 10:46:24 -03:00
X(HTMLOptionElementSelectedChange) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(HTMLSelectElementSetIsOpen) \
LibWeb: Invalidate style (and rule cache) on MediaList changes This makes dynamic changes to a style sheet's media attribute actually take effect immediately.
2025-03-04 10:50:11 -03:00
X(MediaListSetMediaText) \
X(MediaListAppendMedium) \
X(MediaListDeleteMedium) \
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
X(MediaQueryChangedMatchState) \
X(NavigableSetViewportSize) \
X(NodeInsertBefore) \
X(NodeRemove) \
X(NodeSetTextContent) \
X(Other) \
X(SetSelectorText) \
X(SettingsChange) \
X(StyleSheetDeleteRule) \
X(StyleSheetInsertRule) \
X(StyleSheetListAddSheet) \
LibWeb: Remove no-longer-used StyleInvalidationReasons :^)
2025-04-17 09:43:56 -03:00
X(StyleSheetListRemoveSheet)
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
enum class StyleInvalidationReason {
#define __ENUMERATE_STYLE_INVALIDATION_REASON(reason) reason,
ENUMERATE_STYLE_INVALIDATION_REASONS(__ENUMERATE_STYLE_INVALIDATION_REASON)
#undef __ENUMERATE_STYLE_INVALIDATION_REASON
};
LibWeb: Bring back cache of intrinsic sizes across layout runs 12c6ac78e20904431372dec1e81f896807c9f35a with fixed mistake when cache slot is copied instead of being referenced: ```cpp auto cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ``` while it should've been: ```cpp auto& cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ```
2025-03-08 09:52:23 -03:00
#define ENUMERATE_SET_NEEDS_LAYOUT_REASONS(X) \
X(CharacterDataReplaceData) \
X(FinalizeACrossDocumentNavigation) \
LibWeb: Support CSS content property images (and lists, too!) This patch expands our generated content support beyond single strings to lists of strings and/or images. Pseudo-elements like ::before and ::after can now use content:url(...) to insert anonymous image boxes into the layout tree. This is heavily used in Google Docs for UI elements.
2025-07-27 10:55:16 -03:00
X(GeneratedContentImageFinishedLoading) \
LibWeb: Mark canvas element for relayout when width or height changes While width and height are presentational hints on canvas, they actually map to the CSS aspect-ratio attribute, not to CSS width and height. For this reason, we actually need to manually mark for relayout here. Also import a WPT test that was flaky before this change.
2025-05-19 06:04:13 -03:00
X(HTMLCanvasElementWidthOrHeightChange) \
LibWeb: Bring back cache of intrinsic sizes across layout runs 12c6ac78e20904431372dec1e81f896807c9f35a with fixed mistake when cache slot is copied instead of being referenced: ```cpp auto cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ``` while it should've been: ```cpp auto& cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ```
2025-03-08 09:52:23 -03:00
X(HTMLImageElementReactToChangesInTheEnvironment) \
X(HTMLImageElementUpdateTheImageData) \
X(HTMLVideoElementSetVideoTrack) \
X(KeyframeEffect) \
X(LayoutTreeUpdate) \
X(NavigableSetViewportSize) \
X(SVGImageElementFetchTheDocument) \
LibWeb: Implement `<feImage>` SVG filter
2025-08-06 18:52:29 -03:00
X(SVGImageFilterFetch) \
LibWeb: Bring back cache of intrinsic sizes across layout runs 12c6ac78e20904431372dec1e81f896807c9f35a with fixed mistake when cache slot is copied instead of being referenced: ```cpp auto cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ``` while it should've been: ```cpp auto& cache = box.cached_intrinsic_sizes().min_content_height.ensure(width); ```
2025-03-08 09:52:23 -03:00
X(StyleChange)
enum class SetNeedsLayoutReason {
#define ENUMERATE_SET_NEEDS_LAYOUT_REASON(e) e,
ENUMERATE_SET_NEEDS_LAYOUT_REASONS(ENUMERATE_SET_NEEDS_LAYOUT_REASON)
#undef ENUMERATE_SET_NEEDS_LAYOUT_REASON
};
[[nodiscard]] StringView to_string(SetNeedsLayoutReason);
LibWeb: Add debug logging of reasons for layout tree update
2025-04-19 05:49:33 -03:00
#define ENUMERATE_SET_NEEDS_LAYOUT_TREE_UPDATE_REASONS(X) \
X(ElementSetInnerHTML) \
LibWeb: Update the <details> layout tree when it is opened/closed Otherwise, the arrow painted next to the <details> element does not update. Using a screenshot test here because apparently the direction of the arrow has no effect on the layout or paint trees.
2025-05-09 11:35:07 -03:00
X(DetailsElementOpenedOrClosed) \
LibWeb: Add debug logging of reasons for layout tree update
2025-04-19 05:49:33 -03:00
X(HTMLInputElementSrcAttribute) \
LibWeb: Invalidate layout for `ol`-attributes that affect it
2025-05-10 14:08:24 -03:00
X(HTMLOListElementOrdinalValues) \
LibWeb: Add debug logging of reasons for layout tree update
2025-04-19 05:49:33 -03:00
X(HTMLObjectElementUpdateLayoutAndChildObjects) \
X(KeyframeEffect) \
X(NodeInsertBefore) \
X(NodeInsertBeforeWithDisplayContents) \
X(NodeRemove) \
X(NodeSetTextContent) \
X(None) \
X(SVGGraphicsElementTransformChange) \
LibWeb: Update layout when view box properties are changed
2025-08-27 18:19:12 -03:00
X(SVGViewBoxChange) \
LibWeb: Add debug logging of reasons for layout tree update
2025-04-19 05:49:33 -03:00
X(StyleChange)
enum class SetNeedsLayoutTreeUpdateReason {
#define ENUMERATE_SET_NEEDS_LAYOUT_TREE_UPDATE_REASON(e) e,
ENUMERATE_SET_NEEDS_LAYOUT_TREE_UPDATE_REASONS(ENUMERATE_SET_NEEDS_LAYOUT_TREE_UPDATE_REASON)
#undef ENUMERATE_SET_NEEDS_LAYOUT_TREE_UPDATE_REASON
};
[[nodiscard]] StringView to_string(SetNeedsLayoutTreeUpdateReason);
LibWeb: Enable EXPLICIT_SYMBOL_EXPORT
2025-07-19 23:35:33 -03:00
class WEB_API Node : public EventTarget
LibWeb/DOM: Inherit Node from TreeNode This allows to delete lots of tree helper functions duplicated between Node and TreeNode.
2025-02-03 11:25:24 -03:00
, public TreeNode<Node> {
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 08:42:07 -03:00
WEB_PLATFORM_OBJECT(Node, EventTarget);
LibWeb: Start working on DOM event support This patch adds the EventTarget class and makes Node inherit from it. You can register event listeners on an EventTarget, and when you call dispatch_event() on it, the event listeners will get invoked. An event listener is basically a wrapper around a JS::Function*. This is pretty far from how DOM events should eventually work, but it's a place to start and we'll build more on top of this. :^)
2020-03-18 11:22:31 -03: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 08:42:07 -03:00
public:
LibWeb: Add DOM::Node::parent_or_shadow_host() This is useful when you want to traverse across shadow boundaries.
2021-02-10 14:22:20 -03:00
ParentNode* parent_or_shadow_host();
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
ParentNode const* parent_or_shadow_host() const { return const_cast<Node*>(this)->parent_or_shadow_host(); }
LibWeb: Add DOM::Node::parent_or_shadow_host() This is useful when you want to traverse across shadow boundaries.
2021-02-10 14:22:20 -03:00
LibWeb: Add DOM::Node::parent_or_shadow_host_element() This will be used in style computation to inherit style across shadow tree boundaries.
2022-11-05 13:06:19 -03:00
Element* parent_or_shadow_host_element();
Element const* parent_or_shadow_host_element() const { return const_cast<Node*>(this)->parent_or_shadow_host_element(); }
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
virtual ~Node();
NodeType type() const { return m_type; }
bool is_element() const { return type() == NodeType::ELEMENT_NODE; }
LibWeb: Make Node::is_text() return true for CDATASection nodes CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: https://github.com/w3c/DOM-Parsing/issues/38
2024-11-19 11:35:31 -03:00
bool is_text() const { return type() == NodeType::TEXT_NODE || type() == NodeType::CDATA_SECTION_NODE; }
LibWeb: Make Node.normalize() ignore CDATASection nodes We hadn't modeled the "exclusive text node" concept correctly.
2024-11-20 07:31:59 -03:00
bool is_exclusive_text() const { return type() == NodeType::TEXT_NODE; }
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
bool is_document() const { return type() == NodeType::DOCUMENT_NODE; }
LibHTML: Add basic <!DOCTYPE> parsing and a DocumentType class Plus, Document::fixup() will now make sure that the document always starts with a doctype node, followed by an <html> element.
2019-10-09 15:17:01 -03:00
bool is_document_type() const { return type() == NodeType::DOCUMENT_TYPE_NODE; }
LibHTML: Add Comment and CharacterData nodes and improve HTML parsing This patch adds the CharacterData subclass of Node, which is now the parent class of Text and a new Comment class. A Comment node is one of these in HTML: <!--hello friends--> Since these occur somewhat frequently on the web, we need to be able to parse them. This patch also adds a child rejection mechanism to the DOM tree. Nodes can now override is_child_allowed(Node) and return false if they don't want a particular Node to become a child of theirs. This is used to prevent Document from taking on unwanted children.
2019-10-12 18:26:47 -03:00
bool is_comment() const { return type() == NodeType::COMMENT_NODE; }
LibWeb: Calculate length for all `CharacterData` type nodes correctly We now ensure that `Node::is_character_data()` returns true for all nodes of type character data. Previously, calling `Node::length()` on `CDataSection` or `ProcessingInstruction` nodes would return an incorrect value.
2024-07-23 17:55:48 -03:00
bool is_character_data() const { return first_is_one_of(type(), NodeType::TEXT_NODE, NodeType::COMMENT_NODE, NodeType::CDATA_SECTION_NODE, NodeType::PROCESSING_INSTRUCTION_NODE); }
LibHTML: Add DocumentFragment Right now this is just a simple ParentNode subclass with its node type being DOCUMENT_FRAGMENT_NODE.
2019-11-06 16:27:53 -03:00
bool is_document_fragment() const { return type() == NodeType::DOCUMENT_FRAGMENT_NODE; }
LibWeb: Node::is_parent_node() should return true for DocumentFragments
2020-03-25 14:48:10 -03:00
bool is_parent_node() const { return is_element() || is_document() || is_document_fragment(); }
LibWeb: Don't crash when querying the CDataSection.assignedSlot property
2024-03-23 12:46:08 -03:00
bool is_slottable() const { return is_element() || is_text() || is_cdata_section(); }
LibWeb: Make Range.setStart and Range.setEnd spec compliant These functions are way more involved than simply setting their respective boundary points :^)
2022-01-31 15:05:54 -03:00
bool is_attribute() const { return type() == NodeType::ATTRIBUTE_NODE; }
LibWeb: Add CDATASection Not used for anything currently other than exposing it on the Window object. This allows Web Components Polyfills to patch its prototype.
2022-06-27 17:20:59 -03:00
bool is_cdata_section() const { return type() == NodeType::CDATA_SECTION_NODE; }
LibWeb: Add some fast_is<T> helpers for hot classes on GitHub :^)
2022-03-13 13:21:27 -03:00
virtual bool is_shadow_root() const { return false; }
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
LibWeb: Ignore svg elements outside of <svg> when building layout tree An svg layout element without a `SVGSVGElement` ancestor caused a failed assertion before, because the svg context does not exist when `paint()` is called
2021-08-05 05:26:09 -03:00
virtual bool requires_svg_container() const { return false; }
virtual bool is_svg_container() const { return false; }
LibWeb: Add fast way to check if a DOM node is an SVG element
2023-05-24 00:41:55 -03:00
virtual bool is_svg_element() const { return false; }
LibWeb: Add fast_is<SVGGraphicsElement>() This dynamic_cast was ~6% of runtime when mousing around on Discord.
2023-08-03 08:26:29 -03:00
virtual bool is_svg_graphics_element() const { return false; }
LibWeb: Add IDL definition for SVGScriptElement It does not currently handle any of the actual scripting, but this should at least allow us to create an instance of the element. The test being added here isn't actually testing much, but before the previous commit we used to crash parsing the page due to a TODO().
2023-09-22 17:56:49 -03:00
virtual bool is_svg_script_element() const { return false; }
LibWeb: Add method for listing all style sheets on a page This will be used by the inspector, for showing style sheet contents. Identifying a specific style sheet is a bit tricky. Depending on where it came from, a style sheet may have a URL, it might be associated with a DOM element, both, or neither. This varied information is wrapped in a new StyleSheetIdentifier struct.
2024-08-23 06:42:35 -03:00
virtual bool is_svg_style_element() const { return false; }
LibWeb: Add fast_is<SVG::SVGSVGElement>()
2022-03-12 12:08:40 -03:00
virtual bool is_svg_svg_element() const { return false; }
LibWeb: Add fast_is<T>() for SVGUseElement is<SVGUseElement> quite hot in profiles
2023-06-22 20:15:03 -03:00
virtual bool is_svg_use_element() const { return false; }
LibWeb: Implement `SVGViewElement` This identifies a particular region of an SVG image, which can then be linked to by an SVG fragment identifier.
2025-07-12 10:26:50 -03:00
virtual bool is_svg_view_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_svg_a_element() const { return false; }
virtual bool is_svg_foreign_object_element() const { return false; }
LibWeb: Ignore svg elements outside of <svg> when building layout tree An svg layout element without a `SVGSVGElement` ancestor caused a failed assertion before, because the svg context does not exist when `paint()` is called
2021-08-05 05:26:09 -03:00
LibWeb: Add Node::in_a_document_tree() This is "in a document tree" from the DOM spec.
2021-09-29 17:23:28 -03:00
bool in_a_document_tree() const;
LibWeb: Add a couple child node operations to Node and add node types
2021-03-06 14:06:25 -03:00
// NOTE: This is intended for the JS bindings.
u16 node_type() const { return (u16)m_type; }
LibWeb: Refactor "editable" and "editing host" concepts The DOM spec defines what it means for an element to be an "editing host", and the Editing spec does the same for the "editable" concept. Replace our `Node::is_editable()` implementation with these spec-compliant algorithms. An editing host is an element that has the properties to make its contents effectively editable. Editable elements are descendants of an editing host. Concepts like the inheritable contenteditable attribute are propagated through the editable algorithm.
2024-12-06 07:41:20 -03:00
bool is_editable() const;
bool is_editing_host() const;
bool is_editable_or_editing_host() const { return is_editable() || is_editing_host(); }
LibWeb: Change Editing::editing_host_of_node() to Node::editing_host() No functional changes.
2025-07-31 07:29:05 -03:00
GC::Ptr<Node> editing_host();
LibWeb: Only allow editing of elements with contenteditable="true" We now respect the contenteditable HTML attribute and only let you edit content inside explicitly editable elements.
2020-08-02 11:05:59 -03:00
LibJS+LibWeb: Add fast_is<DOM::Node> for JS::Object Solves problem that is<DOM::Node, JS::Object>() is quite hot in profiles while loading https://www.postgresql.org/about/featurematrix/.
2023-07-13 14:54:03 -03:00
virtual bool is_dom_node() const final { return true; }
LibWeb: Add fast_is<HTMLElement>() This avoids slow RTTI lookups in selector matching.
2022-07-27 11:04:31 -03:00
virtual bool is_html_element() const { return false; }
LibWeb: Add fast_is<T>() for HTML::HTMLHtmlElement Another one spotted in a scroll-up-and-down profile.
2021-10-27 12:58:57 -03:00
virtual bool is_html_html_element() const { return false; }
LibWeb: Add fast_is<T> for HTML::HTMLAnchorElement We were spending 20% of style computation time on the HTML spec on deciding whether DOM nodes were HTML anchor (a) tags or not.
2022-03-02 11:14:38 -03:00
virtual bool is_html_anchor_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_html_area_element() const { return false; }
LibWeb: Add fast_is<HTMLBaseElement>() This avoids slow RTTI lookups in Document::base_url().
2022-07-27 11:03:43 -03:00
virtual bool is_html_base_element() const { return false; }
LibWeb: Add fast_is<T>() for various types stood out in a profile
2023-03-10 17:16:18 -03:00
virtual bool is_html_body_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_html_head_element() const { return false; }
LibWeb: Add fast_is<T>() for various types stood out in a profile
2023-03-10 17:16:18 -03:00
virtual bool is_html_input_element() const { return false; }
LibWeb: Add method for listing all style sheets on a page This will be used by the inspector, for showing style sheet contents. Identifying a specific style sheet is a bit tricky. Depending on where it came from, a style sheet may have a URL, it might be associated with a DOM element, both, or neither. This varied information is wrapped in a new StyleSheetIdentifier struct.
2024-08-23 06:42:35 -03:00
virtual bool is_html_link_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_html_media_element() const { return false; }
LibWeb: Add fast_is<T>() for various types stood out in a profile
2023-03-10 17:16:18 -03:00
virtual bool is_html_progress_element() const { return false; }
LibWeb: Add fast_is<T>() helper for HTMLScriptElement This makes loading Google Groups quite a bit faster, as 20% of runtime while loading was spent asking if DOM nodes are HTMLScriptElement.
2023-05-07 02:43:21 -03:00
virtual bool is_html_script_element() const { return false; }
LibWeb: Add method for listing all style sheets on a page This will be used by the inspector, for showing style sheet contents. Identifying a specific style sheet is a bit tricky. Depending on where it came from, a style sheet may have a URL, it might be associated with a DOM element, both, or neither. This varied information is wrapped in a new StyleSheetIdentifier struct.
2024-08-23 06:42:35 -03:00
virtual bool is_html_style_element() const { return false; }
LibWeb: Add fast_is<HTMLTemplateElement>() This was showing up as hot in profiles, as the HTML parser calls it quite a lot.
2021-09-15 19:52:10 -03:00
virtual bool is_html_template_element() const { return false; }
LibWeb: Support fast_is<T>() for table, table sections, rows and cells 3.2x speed-up on WebKit/PerformanceTests/DOM/GridSort.html
2023-08-22 09:55:10 -03:00
virtual bool is_html_table_element() const { return false; }
virtual bool is_html_table_section_element() const { return false; }
virtual bool is_html_table_row_element() const { return false; }
virtual bool is_html_table_cell_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_html_title_element() const { return false; }
LibWeb: Never blockify HTML <br> elements This is a bit iffy, but since <br> elements can't be implemented in "just CSS" today, we should also exclude them from the blockification algorithm. This is important, since <br> is expected to always have inline-like behavior.
2023-09-01 04:55:56 -03:00
virtual bool is_html_br_element() const { return false; }
LibWeb: Use fit-content width if button's computed width is "auto" Implements following line from the spec: "If the computed value of 'inline-size' is 'auto', then the used value is the fit-content inline size."
2023-09-09 12:13:41 -03:00
virtual bool is_html_button_element() const { return false; }
LibWeb: Add fast_is<T>() for HTMLSlotElement 2.4x speed-up on StyleBench :^)
2023-09-23 08:03:59 -03:00
virtual bool is_html_slot_element() const { return false; }
LibWeb: Add fast_is<T> for form, embed, image, and object elements These are used by Window::supported_property_names(), which can get very hot.
2023-12-24 10:41:33 -03:00
virtual bool is_html_embed_element() const { return false; }
virtual bool is_html_object_element() const { return false; }
virtual bool is_html_form_element() const { return false; }
virtual bool is_html_image_element() const { return false; }
LibWeb/HTML: Stop observing lazy-loaded iframes when navigating
2025-01-07 13:06:51 -03:00
virtual bool is_html_iframe_element() const { return false; }
LibWeb: Add fast_is for span and div
2025-04-24 15:09:14 -03:00
virtual bool is_html_div_element() const { return false; }
virtual bool is_html_span_element() const { return false; }
LibWeb: Add more fast_is<T> helpers for DOM::Node subclasses
2025-04-18 05:27:59 -03:00
virtual bool is_html_frameset_element() const { return false; }
virtual bool is_html_fieldset_element() const { return false; }
LibWeb: Add specialized fast_is for lists Before: `is<HTMLOLListElement>` and other similar calls in this commit are resolved to `dynamic_cast`, which incurs runtime overhead for resolving the type. The Performance hit becomes apparent when rendering large lists. Callgrind analysis points to a significant performance hit from calls to `is<...>` in `Element::list_owner`. Reference: Michael Gibbs and Bjarne Stroustrup (2006) Fast dynamic casting. Softw. Pract. Exper. 2006; 36:139–156 After: Implement inline `fast_is` virtual method that immediately resolves the type. Results in noticeable performance improvement 2x-ish for lists with 20K entries. Bonus: Convert starting value for LI elements to signed integer The spec requires the start attribute and starting value to be "integer". Firefox and Chrome support a negative start attribute. FIXME: At the time of this PR, about 134 other objects resolve `is<...>` to `dynamic_cast`. It may be a good idea to coordinate similar changes to at least [some of] the ones that my have impact on performance (maybe open a new issue?).
2025-04-23 11:06:11 -03:00
virtual bool is_html_li_element() const { return false; }
virtual bool is_html_menu_element() const { return false; }
virtual bool is_html_olist_element() const { return false; }
virtual bool is_html_ulist_element() const { return false; }
ALWAYS_INLINE bool is_html_ol_ul_menu_element() const
{
return is_html_olist_element() || is_html_ulist_element() || is_html_menu_element();
}
LibWeb: Rename BrowsingContextContainer => NavigableContainer The "browsing context container" concept in the HTML spec has been replaced with "navigable container". Renaming this is the first step of many towards implementing the new world. Co-authored-by: Aliaksandr Kalenik <kalenik.aliaksandr@gmail.com>
2022-12-12 08:20:02 -03:00
virtual bool is_navigable_container() const { return false; }
LibWeb: Extract shared lazy-loading behavior into a base class `<iframe>` and `<img>` tags share the same spec for several aspects of lazy-loading: how the `loading` attribute works, the "will lazy load element" steps, and a member for storing the lazy-load resumption steps. So let's share the implementation by using a base class. This mostly involves moving things around. However, we also change the `start_intersection_observing_a_lazy_loading_element()` method to take a LazyLoadingElement, and operate on one, instead of always casting to HTMLImageElement. We do unfortunately have to do some shenanigans to make the cast work, by adding a virtual function stub in DOM::Element.
2023-11-21 15:50:09 -03:00
virtual bool is_lazy_loading() const { return false; }
LibWeb: Add fast_is<HTMLTemplateElement>() This was showing up as hot in profiles, as the HTML parser calls it quite a lot.
2021-09-15 19:52:10 -03: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-14 12:01:23 -03:00
WebIDL::ExceptionOr<GC::Ref<Node>> pre_insert(GC::Ref<Node>, GC::Ptr<Node>);
WebIDL::ExceptionOr<GC::Ref<Node>> pre_remove(GC::Ref<Node>);
LibWeb: Make the node mutation algorithms more spec compliant The mutation algorithms now more closely follow the spec and fixes some assertion failures in tests such as Acid3 and Dromaeo. The main thing that is missing right now is passing exceptions to the bindings layer. This is because of issue #6075. I spent a while trying to work it out and got so frustrated I just left it as a FIXME. Besides that, the algorithms bail at the appropriate points. This also makes the adopting steps in the document more spec compliant as it's needed by the insertion algorithm. While I was at it, I added the adoptNode IDL binding. This adds a bunch of ancestor/descendant checks to TreeNode as well. I moved the "remove_all_children" function to Node as it needs to use the full remove algorithm instead of simply removing it from the child list.
2021-04-06 15:34:49 -03: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-14 12:01:23 -03:00
WebIDL::ExceptionOr<GC::Ref<Node>> append_child(GC::Ref<Node>);
WebIDL::ExceptionOr<GC::Ref<Node>> remove_child(GC::Ref<Node>);
LibWeb: Implement Node.removeChild() in terms of "pre-remove" This is what the spec wants us to do.
2022-02-21 18:21:59 -03: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-14 12:01:23 -03:00
void insert_before(GC::Ref<Node> node, GC::Ptr<Node> child, bool suppress_observers = false);
LibWeb: Make the node mutation algorithms more spec compliant The mutation algorithms now more closely follow the spec and fixes some assertion failures in tests such as Acid3 and Dromaeo. The main thing that is missing right now is passing exceptions to the bindings layer. This is because of issue #6075. I spent a while trying to work it out and got so frustrated I just left it as a FIXME. Besides that, the algorithms bail at the appropriate points. This also makes the adopting steps in the document more spec compliant as it's needed by the insertion algorithm. While I was at it, I added the adoptNode IDL binding. This adds a bunch of ancestor/descendant checks to TreeNode as well. I moved the "remove_all_children" function to Node as it needs to use the full remove algorithm instead of simply removing it from the child list.
2021-04-06 15:34:49 -03:00
void remove(bool suppress_observers = false);
void remove_all_children(bool suppress_observers = false);
LibWeb: Make the Node.compareDocumentPosition() return value enum public This will allow other parts of LibWeb to understand these values.
2023-03-30 06:14:26 -03:00
enum DocumentPosition : u16 {
DOCUMENT_POSITION_EQUAL = 0,
DOCUMENT_POSITION_DISCONNECTED = 1,
DOCUMENT_POSITION_PRECEDING = 2,
DOCUMENT_POSITION_FOLLOWING = 4,
DOCUMENT_POSITION_CONTAINS = 8,
DOCUMENT_POSITION_CONTAINED_BY = 16,
DOCUMENT_POSITION_IMPLEMENTATION_SPECIFIC = 32,
};
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-14 12:01:23 -03:00
u16 compare_document_position(GC::Ptr<Node> other);
LibWeb: Expose Node.appendChild() to the web This is a very barebones implementation of appendChild() that doesn't take any of the idiosyncratic DOM behaviors into account yet. Also teach the wrapper generator how to turn an Interpreter argument into a Node&.
2020-06-20 20:00:58 -03: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-14 12:01:23 -03:00
WebIDL::ExceptionOr<GC::Ref<Node>> replace_child(GC::Ref<Node> node, GC::Ref<Node> child);
LibWeb: Implement Node.replaceChild The `if (child->parent())` check seems to be redundant, but I'm keeping it just to match the spec.
2021-05-06 20:52:23 -03:00
LibWeb: Make node cloning methods const
2025-01-11 14:37:08 -03:00
WebIDL::ExceptionOr<GC::Ref<Node>> clone_node(Document* document = nullptr, bool subtree = false, Node* parent = nullptr) const;
WebIDL::ExceptionOr<GC::Ref<Node>> clone_single_node(Document&) const;
LibWeb/DOM: Update node cloning to latest spec Main difference is that a chunk of the "clone a node" steps are pulled out into a "clone a single node" algorithm. Reflects these spec PRs: https://github.com/whatwg/dom/pull/1332 https://github.com/whatwg/dom/pull/1334 Though this code is quite old so there may also be older spec changes included here.
2025-01-03 12:24:30 -03:00
WebIDL::ExceptionOr<GC::Ref<Node>> clone_node_binding(bool subtree);
LibWeb: Implement Node.cloneNode() With this we can now successfully run a Vue.js 2 hello world! :^)
2021-04-13 20:25:10 -03:00
LibWeb: Implement 'State-preserving atomic move integration' This was recently added to both the HTML and DOM specifications, introducing the new moveBefore DOM API, as well as the new internal 'removing steps'. See: * https://github.com/whatwg/html/commit/432e8fb * https://github.com/whatwg/dom/commit/eaf2ac7
2025-03-07 20:45:26 -03:00
WebIDL::ExceptionOr<void> move_node(Node& new_parent, Node* child);
LibWeb: Add a couple child node operations to Node and add node types
2021-03-06 14:06:25 -03:00
// NOTE: This is intended for the JS bindings.
bool has_child_nodes() const { return has_children(); }
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-14 12:01:23 -03:00
GC::Ref<NodeList> child_nodes();
Vector<GC::Root<Node>> children_as_vector() const;
LibWeb: Add a couple child node operations to Node and add node types
2021-03-06 14:06:25 -03:00
LibWeb: Port Node interface from DeprecatedString to String Which is fortunately quite straight forward :^)
2023-09-16 19:51:43 -03:00
virtual FlyString node_name() const = 0;
LibHTML: Add virtual Node::tag_name() This is analogous to the DOM's Node.tagName and makes it easy to ask "hey, what kinda thing is this Node?"
2019-09-28 17:59:16 -03:00
LibWeb: Port Node interface from DeprecatedString to String Which is fortunately quite straight forward :^)
2023-09-16 19:51:43 -03:00
String base_uri() const;
LibWeb: Bring Node closer to spec Node::base_uri() correct implementation was left as a FIXME.
2022-04-12 13:20:13 -03:00
LibWeb: Add an alternative_text() getter This change adds an alternative_text()·getter, for use in computing accessible names.
2024-11-09 11:45:09 -03:00
virtual Optional<String> alternative_text() const;
LibWeb: Port node text content to UTF-16
2025-07-28 10:46:06 -03:00
Utf16String descendant_text_content() const;
Optional<Utf16String> text_content() const;
void set_text_content(Optional<Utf16String> const&);
LibHTML: Add Node::text_content() This returns a String built from all of a Node's text descendants, including itself.
2019-09-29 11:22:15 -03:00
LibWeb: Implement `Node.normalize()` This method puts the given node and all of its sub-tree into a normalized form. A normalized sub-tree has no empty text nodes and no adjacent text nodes.
2024-07-11 17:52:03 -03:00
WebIDL::ExceptionOr<void> normalize();
LibWeb: Port Node interface from DeprecatedString to String Which is fortunately quite straight forward :^)
2023-09-16 19:51:43 -03:00
Optional<String> node_value() const;
void set_node_value(Optional<String> const&);
LibWeb: Implement `Node.nodeValue` DOM attribute
2022-02-18 19:11:43 -03: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-14 12:01:23 -03:00
GC::Ptr<HTML::Navigable> navigable() const;
LibWeb: Implement Node::navigable() https://html.spec.whatwg.org/multipage/document-sequences.html#node-navigable
2023-04-22 18:21:59 -03:00
LibWeb: Implement fragment parsing and use it for Element.innerHTML This patch implements most of the HTML fragment parsing algorithm and ports Element::set_inner_html() to it. This was the last remaining user of the old HTML parser. :^)
2020-06-25 18:42:08 -03:00
Document& document() { return *m_document; }
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
Document const& document() const { return *m_document; }
LibHTML: Make sure every DOM Node belongs to a Document
2019-09-29 06:43:07 -03: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-14 12:01:23 -03:00
GC::Ptr<Document> owner_document() const;
LibWeb: Expose Node.ownerDocument Required by jQuery.
2021-05-02 17:03:50 -03:00
Everywhere: Change west consts caught by clang-format-21 to east consts
2025-08-29 09:02:52 -03:00
HTML::HTMLAnchorElement const* enclosing_link_element() const;
HTML::HTMLElement const* enclosing_html_element() const;
HTML::HTMLElement const* enclosing_html_element_with_attribute(FlyString const&) const;
LibHTML: Implement basic HTMLElement.title support We now show a tooltip for the hovered node's enclosing HTML element's title attribute, if one is present. This patch also adds HTMLHeadingElement. The tags h1-h6 will now create the right kind of objects.
2019-09-29 07:24:36 -03:00
LibWeb: Port node text content to UTF-16
2025-07-28 10:46:06 -03:00
Utf16String child_text_content() const;
LibWeb: Add some helpers to the DOM Node class This patch adds the following things needed by the HTML spec: - Node::child_text_content() - Node::is_connected() - Node::root()
2020-05-24 16:59:24 -03:00
LibWeb: Make Node::root return a reference The root of a node can never be null, as "the root of an object is itself, if its parent is null, or else it is the root of its parent." https://dom.spec.whatwg.org/#concept-tree-root
2021-09-02 15:27:42 -03:00
Node& shadow_including_root();
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
Node const& shadow_including_root() const
LibWeb: Make event dispatching spec-compliant Specification: https://dom.spec.whatwg.org/#concept-event-dispatch This also introduces shadow roots due to it being a requirement of the event dispatcher. However, it does not introduce the full shadow DOM, that can be left for future work. This changes some event dispatches which require certain attributes to be initialised to a value.
2020-11-21 15:32:39 -03:00
{
return const_cast<Node*>(this)->shadow_including_root();
}
LibWeb/DOM: Implement "is closed-shadow-hidden" algorithm
2025-06-16 12:48:15 -03:00
bool is_closed_shadow_hidden_from(Node const&) const;
LibWeb: Add some helpers to the DOM Node class This patch adds the following things needed by the HTML spec: - Node::child_text_content() - Node::is_connected() - Node::root()
2020-05-24 16:59:24 -03:00
bool is_connected() const;
LibWeb: Only react to link element attribute changes when BC connected Link elements that aren't "browsing-context connected" should not trigger a resource fetch when their attributes change. This fixes an issue where we'd waste time by loading every style sheet twice! :^)
2024-04-26 04:29:27 -03:00
[[nodiscard]] bool is_browsing_context_connected() const;
LibWeb: Add Node.parentNode and Node.parentElement to DOM API :^)
2020-06-20 17:26:54 -03:00
Node* parent_node() { return parent(); }
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
Node const* parent_node() const { return parent(); }
LibWeb: Add Node.parentNode and Node.parentElement to DOM API :^)
2020-06-20 17:26:54 -03:00
LibWeb: Make Node::parent_element return GC::Ptr This is useful for people like myself who run with debug mode to more reliably get stacktraces without spinning up a debugger.
2025-04-17 23:19:19 -03:00
GC::Ptr<Element> parent_element();
GC::Ptr<Element const> parent_element() const;
LibWeb: Add Node.parentNode and Node.parentElement to DOM API :^)
2020-06-20 17:26:54 -03:00
LibWeb: Make the node mutation event functions spec compliant This particularly affects the insertion steps and the removed steps. The insertion steps no longer take into the parent that the node was inserted to, as per the spec. Due to this, I have renamed the function from "inserted_into" to simply "inserted". None of the users of the insertion steps was using it anyway. The removed steps now take a pointer to the old parent instead of a reference. This is because it is optional according to the spec and old parent is null when running the removal steps for the descendants of a node that just got removed. This commit does not affect HTMLScriptElement as there is a bit more to that, which is better suited for a separate commit. Also adds in the adopted steps as they will be used later.
2021-04-06 13:58:20 -03:00
virtual void inserted();
LibWeb/DOM: Implement the DOM post connection steps See: https://github.com/whatwg/dom/commit/0616094
2024-12-10 03:34:50 -03:00
virtual void post_connection();
LibWeb: Pass old parent's root to Node::removed_from() This will allow nodes to access the root they've just been removed from.
2025-01-23 13:37:18 -03:00
virtual void removed_from(Node* old_parent, Node& old_root);
LibWeb: Implement 'State-preserving atomic move integration' This was recently added to both the HTML and DOM specifications, introducing the new moveBefore DOM API, as well as the new internal 'removing steps'. See: * https://github.com/whatwg/html/commit/432e8fb * https://github.com/whatwg/dom/commit/eaf2ac7
2025-03-07 20:45:26 -03:00
virtual void moved_from(GC::Ptr<Node> old_parent);
LibWeb: Add metadata to children update steps invocation Currently, this metadata is only provided on the insertion steps, though I believe it would be useful to extend to the other cases as well. This metadata can aid in making optimizations for these steps by providing extra context into the type of change which was made on the child.
2025-01-26 09:16:33 -03:00
struct ChildrenChangedMetadata {
enum class Type {
Inserted,
Removal,
Mutation,
};
Type type {};
GC::Ref<Node> node;
};
// FIXME: It would be good if we could always provide this metadata for use in optimizations.
virtual void children_changed(ChildrenChangedMetadata const*) { }
LibWeb: Make adopted_from no longer take a const Document reference Nodes implementing the adoption steps can modify the passed in document, for example HTMLTemplateElement does so to adopt it's contents into the new document.
2021-07-05 01:33:35 -03:00
virtual void adopted_from(Document&) { }
LibWeb: Make node cloning methods const
2025-01-11 14:37:08 -03:00
virtual WebIDL::ExceptionOr<void> cloned(Node&, bool) const { return {}; }
LibHTML: Add inserted_into() and removed_from() TreeNode callbacks These will be called when a Node or LayoutNode is inserted or removed from a tree. They get the parent node as an argument.
2019-09-29 12:40:39 -03:00
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
Layout::Node const* layout_node() const { return m_layout_node; }
LibWeb: Rename LayoutNode classes and move them into Layout namespace Bring the names of various boxes closer to spec language. This should hopefully make things easier to understand and hack on. :^) Some notable changes: - LayoutNode -> Layout::Node - LayoutBox -> Layout::Box - LayoutBlock -> Layout::BlockBox - LayoutReplaced -> Layout::ReplacedBox - LayoutDocument -> Layout::InitialContainingBlockBox - LayoutText -> Layout::TextNode - LayoutInline -> Layout::InlineNode Note that this is not strictly a "box tree" as we also hang inline/text nodes in the same tree, and they don't generate boxes. (Instead, they contribute line box fragments to their containing block!)
2020-11-22 11:53:01 -03:00
Layout::Node* layout_node() { return m_layout_node; }
LibHTML: Add support for <body bgcolor="#rrggbb" text="#rrggbb"> This patch implements basic support for presentational hints, which are old-school HTML attributes that affect style. You add support for a presentational hint attribute by overriding Element::apply_presentational_hints(StyleProperties&) and setting all of the corresponding CSS properties as appropriate. To make the background color fill the entire document, not just the bounds of the <body> element's LayoutNode, we special-case it in the HtmlView::paint_event() code for now. I'm not entirely sure what the nicest solution would be, but I'm sure we'll discover it eventually.
2019-10-04 16:05:52 -03:00
LibWeb/DOM: Rename Node::{paint => paintable}_box() It returns a PaintableBox, not a 'PaintBox'.
2023-04-20 12:01:16 -03:00
Painting::PaintableBox const* paintable_box() const;
LibWeb: Add non-const version of paintable_box() in DOM::Node
2023-08-06 19:59:23 -03:00
Painting::PaintableBox* paintable_box();
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 18:46:35 -03:00
Painting::Paintable const* paintable() const;
LibWeb: Make Document::paintable() return a ViewportPaintable
2023-08-19 04:29:04 -03:00
Painting::Paintable* paintable();
LibWeb: Add Painting::Box and move things from Layout::Box into it The "paintable" state in Layout::Box was actually not safe to access until after layout had been performed. As a first step towards making this harder to mess up accidentally, this patch moves painting information from Layout::Box to a new class: Painting::Box. Every layout can have a corresponding paint box, and it holds the final used metrics determined by layout. The paint box is created and populated by FormattingState::commit(). I've also added DOM::Node::paint_box() as a convenient way to access the paint box (if available) of a given DOM node. Going forward, I believe this will allow us to better separate data that belongs to layout vs painting, and also open up opportunities for naturally invalidating caches in the paint box (since it's reconstituted by every layout.)
2022-03-09 19:53:41 -03: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-14 12:01:23 -03:00
void set_paintable(GC::Ptr<Painting::Paintable>);
LibWeb: Allow layout nodes to have multiple paintables CSS fragmentation implies 1:N relationship between layout nodes and paintables. This change is a preparation for implementation of inline fragmentation where InlinePaintable will be replaced with PaintableWithLines corresponding to each line.
2024-10-14 11:07:56 -03:00
void clear_paintable();
LibWeb: Give DOM::Node a direct pointer to its Paintable Instead of going via the layout tree.
2023-08-19 07:00:42 -03: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-14 12:01:23 -03:00
void set_layout_node(Badge<Layout::Node>, GC::Ref<Layout::Node>);
LibWeb: Detach stale layout nodes from DOM during layout tree build When toggling `display: none` on an element, it can go from having a layout subtree to not having one. In the `none` case, we were previously leaving stale layout nodes hanging off DOM nodes in the subtree. These layout nodes could be queried for outdated information and probably other things that we shouldn't allow. Fix this by having TreeBuilder prune any old layout nodes hanging off nodes in a subtree after its subtree root doesn't produce a layout node.
2023-08-01 03:23:13 -03:00
void detach_layout_node(Badge<Layout::TreeBuilder>);
LibHTML: Add support for <body bgcolor="#rrggbb" text="#rrggbb"> This patch implements basic support for presentational hints, which are old-school HTML attributes that affect style. You add support for a presentational hint attribute by overriding Element::apply_presentational_hints(StyleProperties&) and setting all of the corresponding CSS properties as appropriate. To make the background color fill the entire document, not just the bounds of the <body> element's LayoutNode, we special-case it in the HtmlView::paint_event() code for now. I'm not entirely sure what the nicest solution would be, but I'm sure we'll discover it eventually.
2019-10-04 16:05:52 -03:00
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
virtual bool is_child_allowed(Node const&) const { return true; }
LibHTML: Add Comment and CharacterData nodes and improve HTML parsing This patch adds the CharacterData subclass of Node, which is now the parent class of Text and a new Comment class. A Comment node is one of these in HTML: <!--hello friends--> Since these occur somewhat frequently on the web, we need to be able to parse them. This patch also adds a child rejection mechanism to the DOM tree. Nodes can now override is_child_allowed(Node) and return false if they don't want a particular Node to become a child of theirs. This is used to prevent Document from taking on unwanted children.
2019-10-12 18:26:47 -03:00
LibWeb: Implement partial layout tree updates DOM nodes now have two additional flags: - Needs layout tree update - Child needs layout tree update These work similarly to the needs-style-update flags, but instead signal the need to rebuild the corresponding part of the layout tree. When a specific DOM node needs a layout tree update, we try to create a new subtree starting at that node, and then replace the subtree in the old layout tree with the newly created subtree. This required some refactoring in TreeBuilder so that we can skip over entire subtrees during a tree update. Note that no partial updates happen yet (as of this commit) since we always invalidate the full layout tree still. That will change in the next commit.
2025-01-13 08:23:40 -03:00
[[nodiscard]] bool needs_layout_tree_update() const { return m_needs_layout_tree_update; }
LibWeb: Add debug logging of reasons for layout tree update
2025-04-19 05:49:33 -03:00
void set_needs_layout_tree_update(bool, SetNeedsLayoutTreeUpdateReason);
LibWeb: Implement partial layout tree updates DOM nodes now have two additional flags: - Needs layout tree update - Child needs layout tree update These work similarly to the needs-style-update flags, but instead signal the need to rebuild the corresponding part of the layout tree. When a specific DOM node needs a layout tree update, we try to create a new subtree starting at that node, and then replace the subtree in the old layout tree with the newly created subtree. This required some refactoring in TreeBuilder so that we can skip over entire subtrees during a tree update. Note that no partial updates happen yet (as of this commit) since we always invalidate the full layout tree still. That will change in the next commit.
2025-01-13 08:23:40 -03:00
[[nodiscard]] bool child_needs_layout_tree_update() const { return m_child_needs_layout_tree_update; }
void set_child_needs_layout_tree_update(bool b) { m_child_needs_layout_tree_update = b; }
LibHTML: Batch style updates and make them start from the root Use a zero-timer to schedule a style update after invalidating style on any node. Nodes now have a needs_style_update flag which helps us batch and coalesce the work. We also start style updates at the root and work our way through the document, updating any node that has the needs_style_update flag set. This is slower than what we were doing before, but far more correct. There is a ton of room for improvement here. :^)
2019-10-19 13:57:02 -03:00
bool needs_style_update() const { return m_needs_style_update; }
LibWeb: Make DOM::Node::set_needs_style_update() schedule the update After you mark a node as needing new style, there's no situation in which we don't want a style update to happen, so just take care of scheduling it automatically.
2020-12-13 11:19:42 -03:00
void set_needs_style_update(bool);
LibWeb: Defer entire-subtree style invalidations Instead of traversing the entire DOM subtrees and marking nodes for style update, this patch adds a new mechanism where we can mark a subtree root as "entire subtree needs style update". A new pass in Document::update_style() then takes care of coalescing all these invalidations in a single traversal of the DOM. This shaves *minutes* of loading time off of https://wpt.fyi/ subpages.
2025-01-26 15:00:51 -03:00
void set_needs_style_update_internal(bool) { m_needs_style_update = true; }
LibHTML: Batch style updates and make them start from the root Use a zero-timer to schedule a style update after invalidating style on any node. Nodes now have a needs_style_update flag which helps us batch and coalesce the work. We also start style updates at the root and work our way through the document, updating any node that has the needs_style_update flag set. This is slower than what we were doing before, but far more correct. There is a ton of room for improvement here. :^)
2019-10-19 13:57:02 -03:00
LibWeb: Limit style update tree traversal to dirty subtrees This patch adds a second style dirty bit that tracks whether a DOM node has one or more children with dirty style. This allows the style update to skip over entire subtrees where all nodes are clean.
2020-12-14 08:04:30 -03:00
bool child_needs_style_update() const { return m_child_needs_style_update; }
void set_child_needs_style_update(bool b) { m_child_needs_style_update = b; }
LibWeb: Defer entire-subtree style invalidations Instead of traversing the entire DOM subtrees and marking nodes for style update, this patch adds a new mechanism where we can mark a subtree root as "entire subtree needs style update". A new pass in Document::update_style() then takes care of coalescing all these invalidations in a single traversal of the DOM. This shaves *minutes* of loading time off of https://wpt.fyi/ subpages.
2025-01-26 15:00:51 -03:00
[[nodiscard]] bool entire_subtree_needs_style_update() const { return m_entire_subtree_needs_style_update; }
void set_entire_subtree_needs_style_update(bool b) { m_entire_subtree_needs_style_update = b; }
LibWeb: Note what's causing a style invalidation to happen You can now build with STYLE_INVALIDATION_DEBUG and get a debug stream of reasons why style invalidations are happening and where. I've rewritten this code many times, so instead of throwing it away once again, I figured we should at least have it behind a flag.
2024-09-04 05:01:08 -03:00
void invalidate_style(StyleInvalidationReason);
LibWeb: Fix underinvalidation when inline style has custom properties We have an optimization that allows us to invalidate only the style of the element itself and mark descendants for inherited properties update when the "style" attribute changes (unless there are any CSS rules that use the "style" attribute, then we also invalidate all descendants that might be affected by those rules). This optimization was not taking into account that when the inline style has custom properties, we also need to invalidate all descendants whose style might be affected by them. This change fixes this bug by saving a flag in Element that indicates whether its style depends on any custom properties and then invalidating all descendants with this flag set when the "style" attribute changes. Unlike font relative lengths invalidation, for elements that depend on custom properties, we need to actually recompute the style, instead of individual properties, because values without expanded custom properties are gone after cascading, and it has to be done again. The test added for this change is a version of an existing test we had restructured such that it doesn't trigger aggressive style invalidation caused by DOM structured changes until the last moment when test results are printed.
2025-01-27 17:19:30 -03:00
struct StyleInvalidationOptions {
bool invalidate_self { false };
};
void invalidate_style(StyleInvalidationReason, Vector<CSS::InvalidationSet::Property> const&, StyleInvalidationOptions);
LibHTML: Implement basic partial style invalidation This patch makes it possible to call Node::invalidate_style() and have that node and all of its ancestors recompute their style. We then figure out if the new style is visually different from the old style, and if so do a paint invalidation with set_needs_display(). Note that the "are they visually different" code is very incomplete! Use this to make hover effects a lot more efficient. They no longer cause a full relayout+repaint, but only a style invalidation. Style invalidations are still quite heavy though, and there's a lot of room for improvement there. :^)
2019-10-14 13:32:02 -03:00
LibWeb: Implement fragment parsing and use it for Element.innerHTML This patch implements most of the HTML fragment parsing algorithm and ports Element::set_inner_html() to it. This was the last remaining user of the old HTML parser. :^)
2020-06-25 18:42:08 -03:00
void set_document(Badge<Document>, Document&);
LibWeb/DOM: Update an attribute's node document Corresponds to https://github.com/whatwg/dom/commit/b64559cc085fe43791f3f386b5a049993b40ec96
2025-02-21 09:01:20 -03:00
void set_document(Badge<NamedNodeMap>, Document&);
LibWeb: Implement fragment parsing and use it for Element.innerHTML This patch implements most of the HTML fragment parsing algorithm and ports Element::set_inner_html() to it. This was the last remaining user of the old HTML parser. :^)
2020-06-25 18:42:08 -03:00
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
virtual EventTarget* get_parent(Event const&) override;
LibWeb: Make event dispatching spec-compliant Specification: https://dom.spec.whatwg.org/#concept-event-dispatch This also introduces shadow roots due to it being a requirement of the event dispatcher. However, it does not introduce the full shadow DOM, that can be left for future work. This changes some event dispatches which require certain attributes to be initialised to a value.
2020-11-21 15:32:39 -03:00
LibWeb: Add fast_is<T>() for some DOM and layout node subclasses The generic is<T>() uses dynamic_cast which is fine in the majority of cases, but when one of them shows up in profiles, we can make it faster by answering the is-a question manually.
2021-01-17 05:34:01 -03:00
template<typename T>
bool fast_is() const = delete;
LibWeb: Throw pre insertion validity errors from the correct global
2025-07-24 23:35:01 -03:00
WebIDL::ExceptionOr<void> ensure_pre_insertion_validity(JS::Realm&, GC::Ref<Node> node, GC::Ptr<Node> child) const;
LibWeb: Make the node mutation algorithms more spec compliant The mutation algorithms now more closely follow the spec and fixes some assertion failures in tests such as Acid3 and Dromaeo. The main thing that is missing right now is passing exceptions to the bindings layer. This is because of issue #6075. I spent a while trying to work it out and got so frustrated I just left it as a FIXME. Besides that, the algorithms bail at the appropriate points. This also makes the adopting steps in the document more spec compliant as it's needed by the insertion algorithm. While I was at it, I added the adoptNode IDL binding. This adds a bunch of ancestor/descendant checks to TreeNode as well. I moved the "remove_all_children" function to Node as it needs to use the full remove algorithm instead of simply removing it from the child list.
2021-04-06 15:34:49 -03:00
Everywhere: Run clang-format
2022-04-01 14:58:27 -03:00
bool is_host_including_inclusive_ancestor_of(Node const&) const;
LibWeb: Make the node mutation algorithms more spec compliant The mutation algorithms now more closely follow the spec and fixes some assertion failures in tests such as Acid3 and Dromaeo. The main thing that is missing right now is passing exceptions to the bindings layer. This is because of issue #6075. I spent a while trying to work it out and got so frustrated I just left it as a FIXME. Besides that, the algorithms bail at the appropriate points. This also makes the adopting steps in the document more spec compliant as it's needed by the insertion algorithm. While I was at it, I added the adoptNode IDL binding. This adds a bunch of ancestor/descendant checks to TreeNode as well. I moved the "remove_all_children" function to Node as it needs to use the full remove algorithm instead of simply removing it from the child list.
2021-04-06 15:34:49 -03:00
LibWeb: Remove Document::is_scripting_enabled() and use Node's There's no need to have a custom is_scripting_enabled() for the Document class, as it (indirectly) inherits from Node. Also, let's not hardcode false here :^)
2022-03-30 18:28:28 -03:00
bool is_scripting_enabled() const;
LibWeb: Check if scripting is disabled before running script This is not a full check, it's just enough to prevent script execution in DOMParser.
2021-07-04 23:59:47 -03:00
bool is_scripting_disabled() const;
LibWeb: Add JSON serialization method to DOM::Node This method builds a JSON object representing the full state of the DOM tree. The JSON that is built will be used for building the DOM Inspector widget for the OutOfProcessWebView.
2021-06-07 12:32:24 -03:00
// Used for dumping the DOM Tree
void serialize_tree_as_json(JsonObjectSerializer<StringBuilder>&) const;
LibWeb/DOM: Serialize pseudo-elements in the correct order Make Element responsible for serializing all its children, so it can put them in order.
2025-07-02 12:13:52 -03:00
IterationDecision serialize_child_as_json(JsonArraySerializer<StringBuilder>& children_array, Node const& child) const;
LibWeb: Add JSON serialization method to DOM::Node This method builds a JSON object representing the full state of the DOM tree. The JSON that is built will be used for building the DOM Inspector widget for the OutOfProcessWebView.
2021-06-07 12:32:24 -03:00
LibWeb: Add shadow including ancestor/descendant checks
2021-09-01 22:17:13 -03:00
bool is_shadow_including_descendant_of(Node const&) const;
bool is_shadow_including_inclusive_descendant_of(Node const&) const;
bool is_shadow_including_ancestor_of(Node const&) const;
bool is_shadow_including_inclusive_ancestor_of(Node const&) const;
LibWeb: Make DOM Node unique IDs strongly typed (and 64 bit) This is strictly nicer than passing them around as i32 everywhere, and by switching to i64 as the underlying type, ID allocation becomes as simple as incrementing an integer.
2024-10-20 05:37:44 -03:00
[[nodiscard]] UniqueNodeID unique_id() const { return m_unique_id; }
static Node* from_unique_id(UniqueNodeID);
LibWeb: Give each Node a unique ID We maintain a directory of ID -> Node. Nodes add themselves to this directory when they are created, receiving a random ID. When a Node is destroyed, it removes itself from this directory. Anyone can request a Node from the directory by its ID using `Node::from_id()`. We reserve the `0` ID to mean "none". These IDs allow different processes to communicate about a given Node over IPC, for example the DOM Inspector.
2021-08-30 11:52:08 -03:00
LibWeb: Move XMLSerializer into HTML directory The DOMParsing spec is in the process of being merged into the HTML one, gradually. The linked spec change moves XMLSerializer, but many of the algorithms are still in the DOMParsing spec so I've left the links to those alone. I've done my best to update the GN build but since I'm not actually using it, I might have done that wrong. Corresponds to https://github.com/whatwg/html/commit/2edb8cc7eefc6b918c181ea470350d9447423819
2025-03-03 10:04:14 -03:00
WebIDL::ExceptionOr<String> serialize_fragment(HTML::RequireWellFormed, FragmentSerializationMode = FragmentSerializationMode::Inner) const;
LibWeb: Implement HTML fragment serialisation and use it in innerHTML The previous implementation was about a half implementation and was tied to Element::innerHTML. This separates it and puts it into HTMLDocumentParser, as this is in the parsing section of the spec. This provides a near finished HTML fragment serialisation algorithm, bar namespaces in attributes and the `is` value.
2021-09-13 18:42:15 -03:00
LibWeb: Implement unsafe HTML parsing methods Both Element's and ShadowRoot's setHTMLUnsafe, and Document's static parseHTMLUnsafe methods are implemented.
2024-06-25 16:55:58 -03:00
WebIDL::ExceptionOr<void> unsafely_set_html(Element&, StringView);
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-14 12:01:23 -03:00
void replace_all(GC::Ptr<Node>);
LibWeb: Port node text content to UTF-16
2025-07-28 10:46:06 -03:00
void string_replace_all(Utf16String);
LibWeb: Implement the (string) replace all operations for Node
2021-09-05 21:25:58 -03:00
LibWeb: Implement Node.isSameNode(Node? otherNode)
2021-09-13 07:49:23 -03:00
bool is_same_node(Node const*) const;
LibWeb: Implement Node.isEqualNode(Node? otherNode)
2021-09-13 07:54:24 -03:00
bool is_equal_node(Node const*) const;
LibWeb: Implement Node.isSameNode(Node? otherNode)
2021-09-13 07:49:23 -03: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-14 12:01:23 -03:00
GC::Ref<Node> get_root_node(GetRootNodeOptions const& options = {});
LibWeb: Implement Node.getRootNode
2021-10-15 23:04:55 -03:00
LibWeb: Hide uninteresting whitespace text nodes from DOM inspector Use a simple heuristic to exclude uninteresting whitespace and de-clutter the inspector's DOM tree. Uninteresting whitespace is currently one of these: - Non-rendered whitespace-only text nodes - Rendered whitespace-only text nodes between block-level elements
2021-11-02 15:20:57 -03:00
bool is_uninteresting_whitespace_node() const;
LibWeb: Port DOM::Node from DeprecatedString
2023-12-02 16:24:04 -03:00
String debug_description() const;
LibWeb: Make DOM inspector overlay rects a little nicer Instead of just the outline, fill them with some semi-transparent color. Also add tag name, ID, classes and coordinates to the little tooltip. Finally, use the border box instead of the context box for metrics, same as other browsers.
2022-02-26 04:18:14 -03:00
LibWeb: Make Range.setStart and Range.setEnd spec compliant These functions are way more involved than simply setting their respective boundary points :^)
2022-01-31 15:05:54 -03:00
size_t length() const;
LibWeb: Only allocate DOM::Node registered observer list on demand Most DOM nodes don't have registered mutation observers, so let's put the metadata about them behind an OwnPtr to save space in the common case. Saves 16 bytes per DOM node that doesn't have registered observers.
2023-11-18 07:22:51 -03:00
auto& registered_observer_list() { return m_registered_observer_list; }
auto const& registered_observer_list() const { return m_registered_observer_list; }
LibWeb: Introduce Mutation{Record,Observer} and observer microtasks
2022-07-11 12:37:51 -03:00
LibWeb: Only allocate DOM::Node registered observer list on demand Most DOM nodes don't have registered mutation observers, so let's put the metadata about them behind an OwnPtr to save space in the common case. Saves 16 bytes per DOM node that doesn't have registered observers.
2023-11-18 07:22:51 -03:00
void add_registered_observer(RegisteredObserver&);
LibWeb: Introduce Mutation{Record,Observer} and observer microtasks
2022-07-11 12:37:51 -03:00
LibWeb+LibWebView+WebContent: Inform the UI about DOM mutations This will allow our DevTools server to inform the Firefox DevTools client about DOM mutations.
2025-03-06 19:32:43 -03:00
void queue_mutation_record(FlyString const& type, Optional<FlyString> const& attribute_name, Optional<FlyString> const& attribute_namespace, Optional<String> const& old_value, Vector<GC::Root<Node>> added_nodes, Vector<GC::Root<Node>> removed_nodes, Node* previous_sibling, Node* next_sibling);
LibWeb: Implement all "childList" mutation records for MutationObserver
2022-07-11 12:39:14 -03:00
LibWeb: Introduce CustomElementRegistry and creating custom elements The main missing feature here is form associated custom elements.
2023-03-29 19:46:18 -03:00
// https://dom.spec.whatwg.org/#concept-shadow-including-inclusive-descendant
template<typename Callback>
LibWeb: Use `TraversalDecision` for multi level Node traversal methods This adds the `SkipChildrenAndContinue` option, where traversal continues but child nodes are not included.
2024-05-04 10:47:04 -03:00
TraversalDecision for_each_shadow_including_inclusive_descendant(Callback);
LibWeb: Introduce CustomElementRegistry and creating custom elements The main missing feature here is form associated custom elements.
2023-03-29 19:46:18 -03:00
LibWeb: Traverse shadow-including subtree when adopting DOM nodes This takes care of two FIXMEs and fixes an issue on Google Docs where we'd mix boxes from different documents in the same layout tree. (This happened because shadow trees remained attached to their old document when their host was adopted.)
2022-07-12 18:13:57 -03:00
// https://dom.spec.whatwg.org/#concept-shadow-including-descendant
template<typename Callback>
LibWeb: Use `TraversalDecision` for multi level Node traversal methods This adds the `SkipChildrenAndContinue` option, where traversal continues but child nodes are not included.
2024-05-04 10:47:04 -03:00
TraversalDecision for_each_shadow_including_descendant(Callback);
LibWeb: Traverse shadow-including subtree when adopting DOM nodes This takes care of two FIXMEs and fixes an issue on Google Docs where we'd mix boxes from different documents in the same layout tree. (This happened because shadow trees remained attached to their old document when their host was adopted.)
2022-07-12 18:13:57 -03:00
LibWeb: Introduce the slottable concept for DOM elements and text nodes A slottable is either a DOM element or a DOM text node. They may be assigned to slots (HTMLSlotElement) either automatically or manually. Automatic assignment occurs by matching a slot's `name` attribute to a slottable's `slot` attribute. Manual assignment occurs by using the slot's (not yet implemented) `assign` API. This commit does not perform the above assignments. It just sets up the slottable concept via IDL and hooks the slottable mixin into the element and text nodes.
2023-09-05 14:07:35 -03:00
Slottable as_slottable();
LibWeb: Add pseudoElement parameter to GetAnimationsOptions This corresponds to: https://github.com/w3c/csswg-drafts/pull/11050 For now, we don't do anything useful with this parameter, because we don't yet support animating pseudo-elements.
2024-11-08 12:41:49 -03:00
template<typename U, typename Callback>
WebIDL::ExceptionOr<void> for_each_child_of_type_fallible(Callback callback)
{
for (auto* node = first_child(); node; node = node->next_sibling()) {
LibWeb/DOM: Use as_if for node of type checks in iteration helpers These are very hot functions in profiles, so let's avoid a potential double dynamic_cast or virtual call. For consistency, port all of these classes of function over to 'as_if' instead.
2025-01-25 22:05:57 -03:00
if (auto* maybe_node_of_type = as_if<U>(node)) {
if (TRY(callback(*maybe_node_of_type)) == IterationDecision::Break)
LibWeb: Add pseudoElement parameter to GetAnimationsOptions This corresponds to: https://github.com/w3c/csswg-drafts/pull/11050 For now, we don't do anything useful with this parameter, because we don't yet support animating pseudo-elements.
2024-11-08 12:41:49 -03:00
return {};
}
}
return {};
}
LibWeb: Allow SVG painting to escape out of a shadow tree The spec for the `<use>` element requires a shadow tree for the rendered content, so we need to be able to escape shadow trees when rendering svg content.
2023-05-28 14:27:35 -03:00
template<typename U>
U const* shadow_including_first_ancestor_of_type() const
{
return const_cast<Node*>(this)->template shadow_including_first_ancestor_of_type<U>();
}
template<typename U>
U* shadow_including_first_ancestor_of_type();
LibWeb: Allow accessible-name computation to skip role-attribute lookup Per https://w3c.github.io/aria/#document-handling_author-errors_roles, determining whether to ignore certain specified landmark roles requires first determining whether the element for which the role is specified has an accessible name. But if we then try to retrieve a role for such elements, we end up calling right back into the accessible-name computation code — which would cause the calls to loop infinitely. So to avoid that — and to have handling for any other future cases the spec may introduce of such recursive calls that will loop indefinitely — this change introduces a parameter that callers can pass to cause role-attribute lookup to be skipped during accessible-name computation.
2024-12-19 11:21:48 -03:00
ErrorOr<String> accessible_name(Document const&, ShouldComputeRole = ShouldComputeRole::Yes) const;
LibWeb: Implement Accessible Name and Description Calculation This is an initial implementation of the accname standard. There is still some of the algorithm left unimplemented that we will need to implement in the future. However, as is, this implementation is sufficient for basic pages.
2023-02-05 14:21:59 -03:00
ErrorOr<String> accessible_description(Document const&) const;
LibWeb: Implement `Node.lookupNamespaceURI()` This method takes a prefix and returns the namespace URI associated with it on the given node, or null if no namespace is found.
2024-07-14 18:50:38 -03:00
Optional<String> locate_a_namespace(Optional<String> const& prefix) const;
Optional<String> lookup_namespace_uri(Optional<String> prefix) const;
LibWeb/DOM: Implement Node.lookupPrefix Adds https://dom.spec.whatwg.org/#dom-node-lookupprefix
2024-07-27 15:51:36 -03:00
Optional<String> lookup_prefix(Optional<String> namespace_) const;
LibWeb: Implement `Node.isDefaultNamespace()` This method accepts a namespace URI as an argument and returns true if the given URI is the default namespace on the given node, false otherwise.
2024-07-17 10:42:45 -03:00
bool is_default_namespace(Optional<String> namespace_) const;
LibWeb: Implement `Node.lookupNamespaceURI()` This method takes a prefix and returns the namespace URI associated with it on the given node, or null if no namespace is found.
2024-07-14 18:50:38 -03:00
LibWeb: Set inertness of HTMLElement when inert attribute is changed
2025-02-05 20:24:47 -03:00
bool is_inert() const;
LibWeb: Cancel animations when element is moved in display none subtree We already have logic to play or cancel animations in an element's subtree when the display property changes to or from none. However, this was not sufficient to cover the case when an element starts/stops being nested in display none after insertion.
2025-03-04 11:32:06 -03:00
bool has_inclusive_ancestor_with_display_none();
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
protected:
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 08:42:07 -03:00
Node(JS::Realm&, Document&, NodeType);
LibHTML: Make sure every DOM Node belongs to a Document
2019-09-29 06:43:07 -03:00
Node(Document&, NodeType);
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
LibWeb/DOM: Update node cloning to latest spec Main difference is that a chunk of the "clone a node" steps are pulled out into a "clone a single node" algorithm. Reflects these spec PRs: https://github.com/whatwg/dom/pull/1332 https://github.com/whatwg/dom/pull/1334 Though this code is quite old so there may also be older spec changes included here.
2025-01-03 12:24:30 -03:00
void set_document(Document&);
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 08:42:07 -03:00
virtual void visit_edges(Cell::Visitor&) override;
LibWeb: Add GC finalizer for DOM::Node Now that the layout tree is also GC-allocated, we can't be messing with it from the DOM::Node destructor. Move everything to a GC finalizer so we know it runs before the GC sweep phase.
2022-10-20 14:30:29 -03:00
virtual void finalize() override;
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 08:42:07 -03: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-14 12:01:23 -03:00
GC::Ptr<Document> m_document;
GC::Ptr<Layout::Node> m_layout_node;
GC::Ptr<Painting::Paintable> m_paintable;
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
NodeType m_type { NodeType::INVALID };
LibWeb: Implement partial layout tree updates DOM nodes now have two additional flags: - Needs layout tree update - Child needs layout tree update These work similarly to the needs-style-update flags, but instead signal the need to rebuild the corresponding part of the layout tree. When a specific DOM node needs a layout tree update, we try to create a new subtree starting at that node, and then replace the subtree in the old layout tree with the newly created subtree. This required some refactoring in TreeBuilder so that we can skip over entire subtrees during a tree update. Note that no partial updates happen yet (as of this commit) since we always invalidate the full layout tree still. That will change in the next commit.
2025-01-13 08:23:40 -03:00
bool m_needs_layout_tree_update { false };
bool m_child_needs_layout_tree_update { false };
LibWeb: Limit style update tree traversal to dirty subtrees This patch adds a second style dirty bit that tracks whether a DOM node has one or more children with dirty style. This allows the style update to skip over entire subtrees where all nodes are clean.
2020-12-14 08:04:30 -03:00
bool m_needs_style_update { false };
bool m_child_needs_style_update { false };
LibWeb: Defer entire-subtree style invalidations Instead of traversing the entire DOM subtrees and marking nodes for style update, this patch adds a new mechanism where we can mark a subtree root as "entire subtree needs style update". A new pass in Document::update_style() then takes care of coalescing all these invalidations in a single traversal of the DOM. This shaves *minutes* of loading time off of https://wpt.fyi/ subpages.
2025-01-26 15:00:51 -03:00
bool m_entire_subtree_needs_style_update { false };
LibWeb: Give each Node a unique ID We maintain a directory of ID -> Node. Nodes add themselves to this directory when they are created, receiving a random ID. When a Node is destroyed, it removes itself from this directory. Anyone can request a Node from the directory by its ID using `Node::from_id()`. We reserve the `0` ID to mean "none". These IDs allow different processes to communicate about a given Node over IPC, for example the DOM Inspector.
2021-08-30 11:52:08 -03:00
LibWeb: Make DOM Node unique IDs strongly typed (and 64 bit) This is strictly nicer than passing them around as i32 everywhere, and by switching to i64 as the underlying type, ID allocation becomes as simple as incrementing an integer.
2024-10-20 05:37:44 -03:00
UniqueNodeID m_unique_id;
LibWeb: Introduce Mutation{Record,Observer} and observer microtasks
2022-07-11 12:37:51 -03:00
// https://dom.spec.whatwg.org/#registered-observer-list
// "Nodes have a strong reference to registered observers in their registered observer list." https://dom.spec.whatwg.org/#garbage-collection
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-14 12:01:23 -03:00
OwnPtr<Vector<GC::Ref<RegisteredObserver>>> m_registered_observer_list;
LibWeb: Implement all "childList" mutation records for MutationObserver
2022-07-11 12:39:14 -03:00
LibWeb: Fix a few const-ness issues
2023-02-25 14:44:51 -03:00
void build_accessibility_tree(AccessibilityTreeNode& parent);
LibWeb: Add Functionality to Dump to Accessibility Tree This will be used to display the accessibility tree in the inspector.
2022-12-11 13:56:37 -03:00
LibWeb: Allow accessible-name computation to skip role-attribute lookup Per https://w3c.github.io/aria/#document-handling_author-errors_roles, determining whether to ignore certain specified landmark roles requires first determining whether the element for which the role is specified has an accessible name. But if we then try to retrieve a role for such elements, we end up calling right back into the accessible-name computation code — which would cause the calls to loop infinitely. So to avoid that — and to have handling for any other future cases the spec may introduce of such recursive calls that will loop indefinitely — this change introduces a parameter that callers can pass to cause role-attribute lookup to be skipped during accessible-name computation.
2024-12-19 11:21:48 -03:00
ErrorOr<String> name_or_description(NameOrDescription, Document const&, HashTable<UniqueNodeID>&, IsDescendant = IsDescendant::No, ShouldComputeRole = ShouldComputeRole::Yes) const;
LibWeb: Implement Accessible Name and Description Calculation This is an initial implementation of the accname standard. There is still some of the algorithm left unimplemented that we will need to implement in the future. However, as is, this implementation is sufficient for basic pages.
2023-02-05 14:21:59 -03:00
LibWeb: Implement all "childList" mutation records for MutationObserver
2022-07-11 12:39:14 -03:00
private:
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-14 12:01:23 -03:00
void queue_tree_mutation_record(Vector<GC::Root<Node>> added_nodes, Vector<GC::Root<Node>> removed_nodes, Node* previous_sibling, Node* next_sibling);
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 08:42:07 -03:00
LibWeb/DOM: Factor out 'live range pre remove steps' AO This was a refactoring made in the DOM spec as part of the introduction of the move before API.
2025-03-07 11:45:12 -03:00
void live_range_pre_remove();
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-14 12:01:23 -03:00
void insert_before_impl(GC::Ref<Node>, GC::Ptr<Node> child);
void append_child_impl(GC::Ref<Node>);
void remove_child_impl(GC::Ref<Node>);
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 08:42:07 -03:00
LibWeb: Port DOM::Node from DeprecatedString
2023-12-02 16:24:04 -03:00
static Optional<StringView> first_valid_id(StringView, Document const&);
LibWeb: Implement Accessible Name and Description Calculation This is an initial implementation of the accname standard. There is still some of the algorithm left unimplemented that we will need to implement in the future. However, as is, this implementation is sufficient for basic pages.
2023-02-05 14:21:59 -03: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-14 12:01:23 -03:00
GC::Ptr<NodeList> m_child_nodes;
LibHTML: Start working on a simple HTML library. I'd like to have rich text, and we might as well use HTML for that. :^)
2019-06-15 13:55:47 -03:00
};
LibHTML: Add is<ElementType> and to<ElementType> helper functions These will help us write node-type-aware template functions.
2019-10-06 15:37:39 -03:00
LibWeb: Move everything into the Web namespace
2020-03-07 06:27:02 -03:00
}
LibJS+LibWeb: Add fast_is<DOM::Node> for JS::Object Solves problem that is<DOM::Node, JS::Object>() is quite hot in profiles while loading https://www.postgresql.org/about/featurematrix/.
2023-07-13 14:54:03 -03:00
template<>
inline bool JS::Object::fast_is<Web::DOM::Node>() const { return is_dom_node(); }
Reference in a new issue Copy permalink