- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 23:44:19 +0000
- To: public-css-archive@w3.org
Note that this does still mean that, if you don't use `per-element`, *every* first instance of `random()` on a particular property across the entire page will share the same random value. That might be a little surprising, but I don't think we can avoid that without violating [the equivalencies I mentioned earlier](https://github.com/w3c/csswg-drafts/issues/11742#issuecomment-2686391413). > Note this introduces more case where we will need to use internal values, raising the priority of https://github.com/w3c/csswg-drafts/issues/8055 ...unless we specify that it's *literally* equivalent to specifying `--margin-1`/etc as the key. Then we can just reflect that directly. I don't see any particular reason that would be bad? It seems unlikely to clash with anything an author actually provides, and it lets them manually hook it if they *do* want to. (That's not *necessary* since they could just *specify the key themselves* and then use it elsewhere, but hey.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11742#issuecomment-2702330006 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 23:44:20 UTC