- From: Sebastian Ühlin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Sep 2018 15:13:29 +0000
- To: public-css-archive@w3.org
One year later and still no result. This feature request is very old and still, in more than 5 years there's no change. My problem isn't that this isn't implemented but rather that the system is not adjusted. Yes, the direction is JS webapps but for html/css websites, this can be a big turningpoint. Done right, it can even lead to more functionality but theres no movement in that direction. Everything gets enhanced. It's CSS right? It has to be unfunctional and static style. I don't know how much restrictions there are to not break compatibility but at some point, either there has to be an alternative to CSS or restrictions should be broken. For me, it doesn't make sense to create an alternative because pseudo classes aren't the problem. It's just a problem that would be caused by the implementation -- GitHub Notification of comment by SEUH Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1656#issuecomment-418142281 using your GitHub account
Received on Monday, 3 September 2018 15:13:31 UTC