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

73 lines
2.3 KiB
C
Raw Permalink 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>
LibWeb: Parse and evaluate `@container` `<size-feature>`s e.g., `@container (width >= 300px) {}` and similar. During style computation, flag any elements whose style depends on a size container. Then re-evaluate their style after the initial layout has been computed and size containers have a size. This may take multiple passes, as these may have further descendants that depend on their size, etc. We limit this to 8 passes currently. SizeFeature itself is very similar to MediaFeature, but queries the container element instead. There are only 6 size features specified, so they're hard-coded instead of generated from JSON. Also add a counter test for the narrower restyle path.
2026-05-14 08:46:17 -03:00
#include <LibWeb/CSS/FeatureQuery.h>
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
namespace Web::CSS {
LibWeb: Parse and evaluate `@container` `<size-feature>`s e.g., `@container (width >= 300px) {}` and similar. During style computation, flag any elements whose style depends on a size container. Then re-evaluate their style after the initial layout has been computed and size containers have a size. This may take multiple passes, as these may have further descendants that depend on their size, etc. We limit this to 8 passes currently. SizeFeature itself is very similar to MediaFeature, but queries the container element instead. There are only 6 size features specified, so they're hard-coded instead of generated from JSON. Also add a counter test for the narrower restyle path.
2026-05-14 08:46:17 -03:00
enum class SizeFeatureID : u8 {
AspectRatio,
BlockSize,
Height,
InlineSize,
Orientation,
Width,
};
// https://drafts.csswg.org/css-conditional-5/#size-container
class SizeFeature final : public FeatureQuery<SizeFeature, SizeFeatureID> {
public:
using Base = FeatureQuery<SizeFeature, SizeFeatureID>;
virtual MatchResult evaluate(BooleanExpressionEvaluationContext const&) const override;
virtual void collect_container_query_feature_requirements(ContainerQueryFeatureRequirements&) const override;
virtual void dump(StringBuilder&, int indent_levels = 0) const override;
static StringView serialize_feature_id(SizeFeatureID);
static bool keyword_is_falsey(SizeFeatureID, Keyword);
private:
friend Base;
SizeFeature(Type type, SizeFeatureID id, Variant<Empty, FeatureValue, Range> value = {})
: Base(type, id, move(value))
{
}
};
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
// 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; }
LibWeb: Parse and evaluate `@container` `<size-feature>`s e.g., `@container (width >= 300px) {}` and similar. During style computation, flag any elements whose style depends on a size container. Then re-evaluate their style after the initial layout has been computed and size containers have a size. This may take multiple passes, as these may have further descendants that depend on their size, etc. We limit this to 8 passes currently. SizeFeature itself is very similar to MediaFeature, but queries the container element instead. There are only 6 size features specified, so they're hard-coded instead of generated from JSON. Also add a counter test for the narrower restyle path.
2026-05-14 08:46:17 -03:00
bool contains_size_feature() const { return m_feature_requirements.contains_size_feature(); }
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
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: Parse and evaluate `@container` `<size-feature>`s e.g., `@container (width >= 300px) {}` and similar. During style computation, flag any elements whose style depends on a size container. Then re-evaluate their style after the initial layout has been computed and size containers have a size. This may take multiple passes, as these may have further descendants that depend on their size, etc. We limit this to 8 passes currently. SizeFeature itself is very similar to MediaFeature, but queries the container element instead. There are only 6 size features specified, so they're hard-coded instead of generated from JSON. Also add a counter test for the narrower restyle path.
2026-05-14 08:46:17 -03:00
Optional<SizeFeatureID> size_feature_id_from_string(StringView);
StringView string_from_size_feature_id(SizeFeatureID);
bool size_feature_type_is_range(SizeFeatureID);
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