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

29 lines
606 B
C++
Raw Normal View History

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
/*
* Copyright (c) 2022, Luke Wilde <lukew@serenityos.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
LibWeb: Remove Bindings/Forward.h from LibWeb/Forward.h This was resulting in a whole lot of rebuilding whenever a new IDL interface was added. Instead, just directly include the prototype in every C++ file which needs it. While we only really need a forward declaration in each cpp file; including the full prototype header (which itself only includes LibJS/Object.h, which is already transitively brought in by PlatformObject) - it seems like a small price to pay compared to what feels like a full rebuild of LibWeb whenever a new IDL file is added. Given all of these includes are only needed for the ::initialize method, there is probably a smart way of avoiding this problem altogether. I've considered both using some macro trickery or generating these functions somehow instead.
2024-04-26 21:09:58 -03:00
#include <LibWeb/Bindings/CDATASectionPrototype.h>
LibWeb: Cleanup unecessary uses and includes of HTML::Window The big global refactor left some stragglers behind for atomicity. Clean up the rest, and remove a ton of includes of LibWeb/HTML/Window.h
2022-09-30 20:16:16 -03:00
#include <LibWeb/Bindings/Intrinsics.h>
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
#include <LibWeb/DOM/CDATASection.h>
namespace Web::DOM {
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_DEFINE_ALLOCATOR(CDATASection);
LibWeb: Put most LibWeb GC objects in type-specific heap blocks With this change, we now have ~1200 CellAllocators across both LibJS and LibWeb in a normal WebContent instance. This gives us a minimum heap size of 4.7 MiB in the scenario where we only have one cell allocated per type. Of course, in practice there will be many more of each type, so the effective overhead is quite a bit smaller than that in practice. I left a few types unconverted to this mechanism because I got tired of doing this. :^)
2023-11-19 15:47:52 -03:00
LibWeb+LibUnicode+WebContent: Port DOM:CharacterData to UTF-16 This replaces the underlying storage of CharacterData with Utf16String and deals with the fallout.
2025-07-24 13:05:52 -03:00
CDATASection::CDATASection(Document& document, Utf16String data)
: Text(document, NodeType::CDATA_SECTION_NODE, move(data))
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
{
}
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
CDATASection::~CDATASection() = default;
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
LibJS: Make Cell::initialize() return void Stop worrying about tiny OOMs. Work towards #20405
2023-08-07 03:41:28 -03:00
void CDATASection::initialize(JS::Realm& realm)
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 08:28:20 -03:00
{
LibWeb: Avoid FlyString lookups when setting IDL interface prototypes This commit introduces a WEB_SET_PROTOTYPE_FOR_INTERFACE macro that caches the interface name in a local static FlyString. This means that we only pay for FlyString-from-literal lookup once per browser lifetime instead of every time the interface is instantiated.
2024-03-16 09:13:08 -03:00
WEB_SET_PROTOTYPE_FOR_INTERFACE(CDATASection);
LibWeb: Only set prototype once for object with IDL interface Before this change, we were going through the chain of base classes for each IDL interface object and having them set the prototype to their prototype. Instead of doing that, reorder things so that we set the right prototype immediately in Foo::initialize(), and then don't bother in all the base class overrides. This knocks off a ~1% profile item on Speedometer 3.
2025-04-20 11:22:57 -03:00
Base::initialize(realm);
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 08:28:20 -03:00
}
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
}
Reference in a new issue Copy permalink