ladybird/Tests/LibWeb/Text/expected/css/CSSStyleDeclaration-custom-properties-2.txt

style.getPropertyValue(--redcolor)=red
style.getPropertyPriority(--redcolor)=
rgb(255, 0, 0)
rgba(0, 0, 0, 0)
LibWeb: Fix underinvalidation when inline style has custom properties We have an optimization that allows us to invalidate only the style of the element itself and mark descendants for inherited properties update when the "style" attribute changes (unless there are any CSS rules that use the "style" attribute, then we also invalidate all descendants that might be affected by those rules). This optimization was not taking into account that when the inline style has custom properties, we also need to invalidate all descendants whose style might be affected by them. This change fixes this bug by saving a flag in Element that indicates whether its style depends on any custom properties and then invalidating all descendants with this flag set when the "style" attribute changes. Unlike font relative lengths invalidation, for elements that depend on custom properties, we need to actually recompute the style, instead of individual properties, because values without expanded custom properties are gone after cascading, and it has to be done again. The test added for this change is a version of an existing test we had restructured such that it doesn't trigger aggressive style invalidation caused by DOM structured changes until the last moment when test results are printed. 2025-01-27 21:19:30 +01:00			`style.getPropertyValue(--redcolor)=red`
			`style.getPropertyPriority(--redcolor)=`
			`rgb(255, 0, 0)`
			`rgba(0, 0, 0, 0)`