- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2021 10:16:25 +0000
- To: public-css-archive@w3.org
I do not have strong expectations that this can move forward. Numerous explanations have been provided as to why this won't happen, and the issue is closed, very deliberately so. It is far from the first time that this gets raised, and the conclusion is always the same, for the same reasons. So most likely, nothing will happen. At the same time, those who believe that closing the issue is a mistake are welcome to try and convince others of that, but repeating arguments that have already been refuted, or acting as if the downsides that have been pointed out don't exist is unlikely to convince anyone. It is possible that most members of the CSSWG and most browser engineers are wrong, that there's a big flaw in the collective reasoning, and that one way or another, this is actually a good idea. If you think so, start by understanding the arguments against, then build a strong case debunking them, and explain why you're right. Merely stating that there's no downside isn't going to be convincing. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/614#issuecomment-777337916 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 February 2021 10:16:27 UTC