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

37 lines
1.1 KiB
C
Raw Normal View History

LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
/*
Everywhere: Use "the SerenityOS developers." in copyright headers We had some inconsistencies before: - Sometimes "The", sometimes "the" - Sometimes trailing ".", sometimes no trailing "." I picked the most common one (lowecase "the", trailing ".") and applied it to all copyright headers. By using the exact same string everywhere we can ensure nothing gets missed during a global search (and replace), and that these inconsistencies are not spread any further (as copyright headers are commonly copied to new files).
2021-04-28 22:46:44 +02:00
* Copyright (c) 2020, the SerenityOS developers.
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
*
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-04-22 01:24:48 -07:00
* SPDX-License-Identifier: BSD-2-Clause
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
*/
#pragma once
LibWeb: Implement HTMLFrameElement as a NavigableContainer NavigableContainer is our home grown concept which already contains the AOs needed for frame and iframe elements. This patch simply aligns our HTMLFrameElement implementation with this class. A couple of notes: 1. The <script> in the <head> element is intentional. The <frameset> element effectively takes the place of the <body> element, and we cannot add a <script> to a <frameset> element. 2. We don't render <frameset> or <frame> at all. Rendering is defined in the following spec: https://html.spec.whatwg.org/multipage/rendering.html#frames-and-framesets 3. If you load the test page in your browser, you won't see anything, regardless of (2). Our test infra adds a <pre> element to the "body" element (which is the <frameset> element here). Such children will never be rendered. In the future, we could come up with something better for our test infra to do, but this isn't important anyways for this test - we can still grab the <pre> element's innerText.
2024-11-03 21:02:07 -05:00
#include <LibWeb/HTML/NavigableContainer.h>
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
namespace Web::HTML {
// NOTE: This element is marked as obsolete, but is still listed as required by the specification.
LibWeb: Implement HTMLFrameElement as a NavigableContainer NavigableContainer is our home grown concept which already contains the AOs needed for frame and iframe elements. This patch simply aligns our HTMLFrameElement implementation with this class. A couple of notes: 1. The <script> in the <head> element is intentional. The <frameset> element effectively takes the place of the <body> element, and we cannot add a <script> to a <frameset> element. 2. We don't render <frameset> or <frame> at all. Rendering is defined in the following spec: https://html.spec.whatwg.org/multipage/rendering.html#frames-and-framesets 3. If you load the test page in your browser, you won't see anything, regardless of (2). Our test infra adds a <pre> element to the "body" element (which is the <frameset> element here). Such children will never be rendered. In the future, we could come up with something better for our test infra to do, but this isn't important anyways for this test - we can still grab the <pre> element's innerText.
2024-11-03 21:02:07 -05:00
class HTMLFrameElement final : public NavigableContainer {
WEB_PLATFORM_OBJECT(HTMLFrameElement, NavigableContainer);
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC_DECLARE_ALLOCATOR(HTMLFrameElement);
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
public:
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
virtual ~HTMLFrameElement() override;
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
LibWeb+LibJS: Make the EventTarget hierarchy (incl. DOM) GC-allocated This is a monster patch that turns all EventTargets into GC-allocated PlatformObjects. Their C++ wrapper classes are removed, and the LibJS garbage collector is now responsible for their lifetimes. There's a fair amount of hacks and band-aids in this patch, and we'll have a lot of cleanup to do after this.
2022-08-28 13:42:07 +02:00
private:
LibWeb: Move QualifiedName into the Web::DOM namespace
2022-02-18 21:00:52 +01:00
HTMLFrameElement(DOM::Document&, DOM::QualifiedName);
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
LibJS: Make Cell::initialize() return void Stop worrying about tiny OOMs. Work towards #20405
2023-08-07 08:41:28 +02:00
virtual void initialize(JS::Realm&) override;
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
LibWeb: Implement HTMLOrSVGElement.tabIndex
2022-11-05 03:58:14 +00:00
// ^DOM::Element
LibWeb: Implement HTMLFrameElement as a NavigableContainer NavigableContainer is our home grown concept which already contains the AOs needed for frame and iframe elements. This patch simply aligns our HTMLFrameElement implementation with this class. A couple of notes: 1. The <script> in the <head> element is intentional. The <frameset> element effectively takes the place of the <body> element, and we cannot add a <script> to a <frameset> element. 2. We don't render <frameset> or <frame> at all. Rendering is defined in the following spec: https://html.spec.whatwg.org/multipage/rendering.html#frames-and-framesets 3. If you load the test page in your browser, you won't see anything, regardless of (2). Our test infra adds a <pre> element to the "body" element (which is the <frameset> element here). Such children will never be rendered. In the future, we could come up with something better for our test infra to do, but this isn't important anyways for this test - we can still grab the <pre> element's innerText.
2024-11-03 21:02:07 -05:00
virtual void inserted() override;
virtual void removed_from(Node*) override;
LibWeb: Consolidate the attribute change handlers We currently have 2 virtual methods to inform DOM::Element subclasses when an attribute has changed, one of which is spec-compliant. This patch removes the non-compliant variant.
2024-11-14 08:14:16 -05:00
virtual void attribute_changed(FlyString const& name, Optional<String> const& old_value, Optional<String> const& value, Optional<FlyString> const& namespace_) override;
LibWeb: Implement HTMLOrSVGElement.tabIndex
2022-11-05 03:58:14 +00:00
virtual i32 default_tab_index_value() const override;
LibWeb: Compute `display: contents` as `none` for unusual elements https://drafts.csswg.org/css-display-3/#unbox-html specifies certain elements that have their `display` style computed as `none` when specified as `contents`. This fixes at least one WPT test: http://wpt.live/css/css-display/display-contents-suppression-dynamic-001.html
2024-11-08 20:14:37 +08:00
virtual void adjust_computed_style(CSS::StyleProperties&) override;
LibWeb: Implement HTMLFrameElement as a NavigableContainer NavigableContainer is our home grown concept which already contains the AOs needed for frame and iframe elements. This patch simply aligns our HTMLFrameElement implementation with this class. A couple of notes: 1. The <script> in the <head> element is intentional. The <frameset> element effectively takes the place of the <body> element, and we cannot add a <script> to a <frameset> element. 2. We don't render <frameset> or <frame> at all. Rendering is defined in the following spec: https://html.spec.whatwg.org/multipage/rendering.html#frames-and-framesets 3. If you load the test page in your browser, you won't see anything, regardless of (2). Our test infra adds a <pre> element to the "body" element (which is the <frameset> element here). Such children will never be rendered. In the future, we could come up with something better for our test infra to do, but this isn't important anyways for this test - we can still grab the <pre> element's innerText.
2024-11-03 21:02:07 -05:00
void process_the_frame_attributes(bool initial_insertion = false);
LibWeb: Add all HTML elements between A and F
2020-08-01 03:04:26 +01:00
};
}
Reference in a new issue Copy permalink