6 commits

Author	SHA1	Message	Date
Sam Atkins	7be645a091	LibWeb/CSS: Implement CSSNumericType.equals()	2025-08-29 11:57:10 +02:00
Sam Atkins	277117eed5	LibWeb/CSS: Implement CSSNumericValue.parse() ... Reifying the result gets quite ad-hoc. Firstly because "parse a component value" produces a ComponentValue, not a full StyleValue like we need for math functions. And second, because not all math functions can be reified as a CSSNumericValue: Besides the fact that I haven't implemented CalculatedStyleValue reification at all yet, there are a lot of math functions with no corresponding CSSMathValue in the spec yet. If the calculation tree contains any of those, the best we can do is reify as a CSSStyleValue, and that isn't a valid return value from CSSNumericValue.parse(). So, I made us throw a SyntaxError in those cases. This seems to match Chrome's behaviour. Spec issue: https://github.com/w3c/css-houdini-drafts/issues/1090	2025-08-29 11:57:10 +02:00
Sam Atkins	6c8876cdb8	LibWeb/CSS: Implement CSSMathValue ... This is a base class for the various math functions, so it's not used directly anywhere.	2025-08-29 11:57:10 +02:00
Sam Atkins	46b55f0f46	LibWeb/CSS: Implement rectify_a_numberish_value()	2025-08-29 11:57:10 +02:00
Sam Atkins	5384338788	LibWeb/CSS: Implement CSSUnitValue	2025-08-22 09:48:30 +01:00
Sam Atkins	6cb8e92bd4	LibWeb/CSS: Stub out CSSNumericValue ... Most of the methods on this rely on its subclasses existing, so for now it's very basic.	2025-08-22 09:48:30 +01:00