Re: [csswg-drafts] [css-values-5] Maybe min, max and step should not be part of the random-caching-key (#11742)

As an author, I prefer more randomness as the default, with options to opt-into shared values - so I really like the change from `per-element` to `match-element` (or similar). Most of my use-cases would involve applying randomness to a list of items, and ideally getting different values per item. With the original proposal, I would be opting into the per-element behavior most of the time.

Without referencing spec lingo, I don't see `match-element` as a confusing name - I would never think of it as matching the unique element identity – but something like `element-shared` does seem even more clear.

I also love @kbabbitt's per-iteration use-case. I would use per-iteration behavior with or without element sharing. I'm not sure I've entirely tracked if either of those is already possible in the proposal. 

-- 
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11742#issuecomment-2737755067 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 March 2025 19:13:19 UTC