5 commits

Author	SHA1	Message	Date
Sam Atkins	a139ad1c44	LibWeb/CSS: Implement CSSNumericValue.to() ... Tries to convert the CSSNumericValue to a CSSUnitValue with the given unit. This gets us the remaining 11 WPT subtests for this method.	2025-09-12 13:45:41 +02:00
Sam Atkins	7be645a091	LibWeb/CSS: Implement CSSNumericType.equals()	2025-08-29 11:57:10 +02:00
Sam Atkins	9264f540dd	LibWeb/CSS: Correct definition of CSSNumericType ... What I thought was a spec issue was actually a combination of my own misunderstanding and a bug in our IDL generator. With that bug fixed, I can correct this to how it is in the spec.	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	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