4 commits

Author	SHA1	Message	Date
Sam Atkins	c3437bccb3	LibWeb: Handle dependency cycles in CSS var()s :^) ... We now detect situations like this, where variables infinitely recur, without crashing: ```css div { --a: var(--b); --b: var(--a); background: var(--a); } p { --foo: var(--foo); background: var(--foo); } ```	2021-12-09 21:30:31 +01:00
Sam Atkins	67e1125b4c	LibWeb: Handle fallback values for CSS variables :^)	2021-12-09 21:30:31 +01:00
Sam Atkins	23dc0dac88	LibWeb: Parse and resolve UnresolvedStyleValues ... If a property is custom or contains a `var()` reference, it cannot be parsed into a proper StyleValue immediately, so we store it as an UnresolvedStyleValue until the property is compute. Then, at compute time, we resolve them by expanding out any `var()` references, and parsing the result. The implementation here is very naive, and involves copying the UnresolvedStyleValue's tree of StyleComponentValueRules while copying the contents of any `var()`s it finds along the way. This is quite an expensive operation to do every time that the style is computed.	2021-12-09 21:30:31 +01:00
Andreas Kling	f8dd3e14ba	LibWeb: Rename CSS::StyleResolver => StyleComputer ... Resolved style is a spec concept that refers to the weird mix of computed style and used style reflected by getComputedStyle(). The purpose of this class is to produce the *computed* style for a given element, so let's call it StyleComputer.	2021-09-24 15:12:15 +02:00

Renamed from Userland/Libraries/LibWeb/CSS/StyleResolver.h (Browse further)