Files
ladybird/Libraries/LibWeb/MathML/MathMLMiElement.h
Tim Ledbetter d1fc4b4234 LibWeb: Route presentational hints through the CSS cascade
Previously, presentational hints bypassed the regular cascade pipeline
and wrote directly into `CascadedProperties` under
`CascadeOrigin::Author`. That meant `var()` substitution and the
invalid-at-computed-value-time fallback had to be duplicated in a
separate per-element pass, which in practice missed the IACVT step and
could leave a `GuaranteedInvalidStyleValue` in the cascaded
properties. This caused a crash in downstream code that assumed the
value had been resolved.

This introduces an `AuthorPresentationalHint` cascade origin and feeds
them through the cascade as normal declarations. This means that
`var()` resolution now happens in only one place.
2026-04-30 19:50:28 +01:00

28 lines
657 B
C++

/*
* Copyright (c) 2025, Lorenz Ackermann, <me@lorenzackermann.xyz>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
#include <LibWeb/MathML/MathMLElement.h>
namespace Web::MathML {
class MathMLMiElement final : public MathMLElement {
WEB_NON_IDL_PLATFORM_OBJECT(MathMLMiElement, MathMLElement);
GC_DECLARE_ALLOCATOR(MathMLMiElement);
public:
virtual ~MathMLMiElement() override = default;
private:
MathMLMiElement(DOM::Document&, DOM::QualifiedName);
virtual bool is_presentational_hint(FlyString const&) const override;
virtual void apply_presentational_hints(Vector<CSS::StyleProperty>&) const override;
};
}