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

38 lines
1.1 KiB
C
Raw Normal View History

LibWeb/CSS: Implement CSSContainerRule No parsing yet, just CSSContainerRule and the supporting ContainerQuery class. CSSContainerRule is unusual in how it matches, because instead of it either matching or not matching globally, it instead is matched against a specific element. But also, some at-rules inside it always apply, as if they were written outside it. This doesn't fit well with how CSSConditionRule is implemented, and will likely require some rework later. For now, `condition_matches()` always returns false, and `for_each_effective_rule()` is overridden to always process those global at-rules and nothing else.
2026-03-27 11:14:00 -03:00
/*
* Copyright (c) 2026, Sam Atkins <sam@ladybird.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
#include <AK/NonnullOwnPtr.h>
#include <AK/RefCounted.h>
#include <LibWeb/CSS/BooleanExpression.h>
namespace Web::CSS {
// https://drafts.csswg.org/css-conditional-5/#container-rule
class WEB_API ContainerQuery final : public RefCounted<ContainerQuery> {
public:
static NonnullRefPtr<ContainerQuery> create(NonnullOwnPtr<BooleanExpression>&&);
bool matches() const { return m_matches; }
LibWeb: Implement ContainerQuery evaluation ContainerQuery now stores its feature requirements. When evaluated, it uses these and the passed-in container name to identify a container element to match against, then evaluates its condition against that element. None of this is yet in use anywhere, but will be soon.
2026-05-08 10:56:28 -03:00
ContainerQueryFeatureRequirements const& feature_requirements() const { return m_feature_requirements; }
MatchResult evaluate(DOM::AbstractElement const&, Optional<FlyString> const& container_name) const;
LibWeb/CSS: Implement CSSContainerRule No parsing yet, just CSSContainerRule and the supporting ContainerQuery class. CSSContainerRule is unusual in how it matches, because instead of it either matching or not matching globally, it instead is matched against a specific element. But also, some at-rules inside it always apply, as if they were written outside it. This doesn't fit well with how CSSConditionRule is implemented, and will likely require some rework later. For now, `condition_matches()` always returns false, and `for_each_effective_rule()` is overridden to always process those global at-rules and nothing else.
2026-03-27 11:14:00 -03:00
String to_string() const;
void dump(StringBuilder&, int indent_levels = 0) const;
private:
explicit ContainerQuery(NonnullOwnPtr<BooleanExpression>&&);
NonnullOwnPtr<BooleanExpression> m_condition;
LibWeb: Implement ContainerQuery evaluation ContainerQuery now stores its feature requirements. When evaluated, it uses these and the passed-in container name to identify a container element to match against, then evaluates its condition against that element. None of this is yet in use anywhere, but will be soon.
2026-05-08 10:56:28 -03:00
ContainerQueryFeatureRequirements m_feature_requirements;
LibWeb/CSS: Implement CSSContainerRule No parsing yet, just CSSContainerRule and the supporting ContainerQuery class. CSSContainerRule is unusual in how it matches, because instead of it either matching or not matching globally, it instead is matched against a specific element. But also, some at-rules inside it always apply, as if they were written outside it. This doesn't fit well with how CSSConditionRule is implemented, and will likely require some rework later. For now, `condition_matches()` always returns false, and `for_each_effective_rule()` is overridden to always process those global at-rules and nothing else.
2026-03-27 11:14:00 -03:00
bool m_matches { false };
};
LibWeb: Implement ContainerQuery evaluation ContainerQuery now stores its feature requirements. When evaluated, it uses these and the passed-in container name to identify a container element to match against, then evaluates its condition against that element. None of this is yet in use anywhere, but will be soon.
2026-05-08 10:56:28 -03:00
bool container_name_matches(DOM::Element const&, Optional<FlyString> const& container_name);
LibWeb/CSS: Implement CSSContainerRule No parsing yet, just CSSContainerRule and the supporting ContainerQuery class. CSSContainerRule is unusual in how it matches, because instead of it either matching or not matching globally, it instead is matched against a specific element. But also, some at-rules inside it always apply, as if they were written outside it. This doesn't fit well with how CSSConditionRule is implemented, and will likely require some rework later. For now, `condition_matches()` always returns false, and `for_each_effective_rule()` is overridden to always process those global at-rules and nothing else.
2026-03-27 11:14:00 -03:00
}
Reference in a new issue Copy permalink