ladybird/Libraries/LibWeb/Painting/NavigableContainerViewportPaintable.h
Aliaksandr Kalenik 568b7ce7ea LibWeb: Make Paintable tree ref-counted
The Paintable tree and its supplemental painting data structures were
GC allocated because that was the easiest way to manage it and avoid
leaks introduced by ref cycles. This included the Paintable subclasses
themselves plus StackingContext, ChromeWidget, Scrollbar, ResizeHandle,
and scroll-frame state.

We are now trying to reduce GC allocation churn on layout and painting
updates, so keeping this short-lived rendering tree outside the JS heap
is a better fit. Move Paintable to RefCountedTreeNode, make painting
helpers ref-counted or weakly reference Paintables, and update the
layout and event-handler call sites to use RefPtr/WeakPtr ownership.
2026-05-07 15:03:44 +02:00

32 lines
1 KiB
C++

/*
* Copyright (c) 2022, Andreas Kling <andreas@ladybird.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
#include <LibWeb/Layout/NavigableContainerViewport.h>
#include <LibWeb/Painting/PaintableBox.h>
namespace Web::Painting {
class NavigableContainerViewportPaintable final : public PaintableBox {
public:
virtual bool is_navigable_container_viewport_paintable() const override { return true; }
static NonnullRefPtr<NavigableContainerViewportPaintable> create(Layout::NavigableContainerViewport const&);
virtual StringView class_name() const override { return "NavigableContainerViewportPaintable"sv; }
virtual void paint(DisplayListRecordingContext&, PaintPhase) const override;
auto const& navigable_container() const { return as<HTML::NavigableContainer>(*dom_node()); }
private:
NavigableContainerViewportPaintable(Layout::NavigableContainerViewport const&);
};
template<>
inline bool Paintable::fast_is<NavigableContainerViewportPaintable>() const { return is_navigable_container_viewport_paintable(); }
}