- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Sep 2023 22:04:21 +0000
- To: public-css-archive@w3.org
As an author, I would really-really want almost everything proposed in this issue and the comments below. In 2020 I did propose to make some of the fields in `@property` optional (https://github.com/w3c/css-houdini-drafts/issues/994), but my attempt was not successful at that time. Maybe this issue could lead to us having a better way to define both custom properties, and global immutable tokens in a much more convenient way. One thing I want to add/ask: does someone know of any benchmarks/research on how the inheritance of the custom properties impacts performance? What could be potential gains from a situation where we, let's say, convert a thousand of design-tokens from a `:root` defined just as `--foo`, this being inheritable, to immutable global env variables, from a browser engine standpoint? Probably could be tested right now with the `@property`, but we don't have any good tools in the current browser developer tools to measure this outside of the “black box” that is currently all the style recalculation/layout boxes in the performance flamegraphs. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9206#issuecomment-1703369736 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 September 2023 22:04:23 UTC