- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Sep 2023 17:51:18 +0000
- To: public-css-archive@w3.org
Discussing with @fantasai - it seems like there are some brevity/consistency advantages to the property approach, but also a potential 'traffic jam' when authors across multiple components/style-sheets all want different timeliness on e.g. the root element. Multiple timelines on a single container would either override each other, or need to be carefully coordinated in a list declaration. If we use an at-rule for defining timelines instead, we avoid that issue – though we're also cluttering a global namespace. It's not clear to us that the property approach is necessarily the better one for this use-case? Consider also that we're not necessarily limited to size-axis queries on containers, but could potentially respond to style queries as well – the size of a font, etc. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6245#issuecomment-1712029991 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 September 2023 17:51:21 UTC