- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 26 Aug 2025 22:11:45 +0000
- To: public-css-archive@w3.org
Thinking about this a little more, an issue is that setting a "starting" seed (like in the [Seeded Random JS proposal](https://github.com/tc39/proposal-seeded-random/)) isn't enough, because the order that CSS values are evaluated in neither defined nor observable, but you need a stable ordering for the random state to evolve predictably. The only thing we could realistically do is just force the random generator's state to be *constant* for all random() calls, but that's identical in practice to just supplying a fixed random base value, like you can do with `fixed`. That might be something we could provide, fwiw - an override that takes a single value between 0 and 1 and forces all random functions to use that as their random base value, regardless of the caching options specified. It would produce potentially undesired behavior, though, like making code intended to generate "random rectangles" instead generate random squares. Would that satisfy the use-case? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12072#issuecomment-3225885428 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 August 2025 22:11:46 UTC