- From: inoas via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Mar 2018 08:59:24 +0000
- To: public-css-archive@w3.org
Use JS(*) for that. While I use :hover, :target and :checked a lot I don't think behavioral things should be in CSS (neither should be :active or :visited). In fact I think behavioral CSS should be deprecated and be disable-able. So: Adding more of these doesn't sound like a good idea to me. (*) *My 2 cents: JS still has its big issues in terms of language design, privacy and performance (DOM), but: use JS for behavior, not CSS; And if all it means is toggling classes - that's OK! However: All built-in browser JS libraries and JS std-lib functions should really become bundled into standardized modules so that for privacy (or preformance) reasons people can disable whole modules/parts of JS/JS-browser-std-lib easily. If done well using HTML for semantic structure, CSS for layouting and JS for behavior/interaction becomes a sane thing again* -- GitHub Notification of comment by inoas Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1656#issuecomment-373305499 using your GitHub account
Received on Thursday, 15 March 2018 09:09:27 UTC