- From: Patrick Brosset via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Oct 2022 18:43:50 +0000
- To: public-css-archive@w3.org
What a thread. Thanks so much to all the amazing people who shared their knowledge and ideas here. This made my day. A few thoughts of my own, since this issue is still open: * A community group was started but after looking at the mailing list, it seems empty. Has anything happened on this topic since the last comment on this thread? Is there a place I can catch up on the most recent discussion? In particular, I'd be interested in knowing if progress has been made in identifying a set of features. * I agree with the benefits people have listed so far in favor of a CSS version, whatever its name. This would do a lot of good in our industry. * I'm of the opinion that this "version" of CSS shouldn't worry too much about whether the features are implemented in engines, and how many. If this marketing term comes out of the Working Group, then it makes sense for it to be more spec-driven than implementation-driven. Meaning: these are the features the WG considers to be version N of CSS. It's not a snapshot of everything, and it may or may not be 100% implemented in engines, but it's a cohesive thing we can easily name, which makes sense, which we can learn about, build courses about, adopt, implement, etc. -- GitHub Notification of comment by captainbrosset Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-1276589815 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 October 2022 18:43:52 UTC