Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: c4182c1faa92daf4f2e654daff0eec1f3d4aa95f
https://github.com/WebKit/WebKit/commit/c4182c1faa92daf4f2e654daff0eec1f3d4aa95f
Author: Joanne Pan <[email protected]>
Date: 2026-08-13 (Thu, 13 Aug 2026)
Changed paths:
M
LayoutTests/imported/w3c/web-platform-tests/css/css-values/random-computed.tentative-expected.txt
M
LayoutTests/imported/w3c/web-platform-tests/css/css-values/random-computed.tentative.html
Log Message:
-----------
[css-values-5] Add test coverage for the random() caching key in custom
properties
https://bugs.webkit.org/show_bug.cgi?id=319266
rdar://182135083
Reviewed by Tim Nguyen.
319039@main allowed random() inside a custom property and 319096@main added the
custom property name to the caching key. Nothing pinned which random() usages
are supposed to share a base value once that works, so add cases for the caching
identity: two registered <length> custom properties on one element, the same
custom property on two elements, a custom property against a non-custom one at
the same index, property-scoped equality across elements, two random() functions
within one custom property, and an author <dashed-ident> that happens to name
the
property an implicit key is scoped to.
The @property initial-value case read the computed value with bracket access on
the CSSStyleDeclaration, which never resolves a custom property, so it compared
undefined to undefined and could not fail. Read it with getPropertyValue() and
assert the property is left unregistered.
*
LayoutTests/imported/w3c/web-platform-tests/css/css-values/random-computed.tentative-expected.txt:
*
LayoutTests/imported/w3c/web-platform-tests/css/css-values/random-computed.tentative.html:
Canonical link: https://commits.webkit.org/319131@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications