mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-05-03 21:12:08 +02:00
e4e3c46837
Node.cpp still contained the policy for deciding when a DOM mutation should schedule pending :has() invalidation work. Move that into CSS::Invalidation::HasMutationInvalidator, next to the mutation feature collector it depends on. This keeps DOM mutation code focused on reporting that a mutation happened, while CSS invalidation code owns the selector-specific checks for :has() metadata and sibling-combinator sensitivity.
23 lines
395 B
C++
23 lines
395 B
C++
/*
|
|
* Copyright (c) 2026-present, the Ladybird developers
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibWeb/DOM/StyleInvalidationReason.h>
|
|
|
|
namespace Web::DOM {
|
|
|
|
class Node;
|
|
|
|
}
|
|
|
|
namespace Web::CSS::Invalidation {
|
|
|
|
void schedule_has_invalidation_for_node(DOM::Node&, DOM::StyleInvalidationReason);
|
|
void schedule_has_invalidation_for_same_parent_move(DOM::Node&);
|
|
|
|
}
|