3 ms·
Where is the rule that people need to complain about JavaScript at least once for every post?
by schwartzworld 4y ago
Where is the rule that people need to complain about JavaScript at least once for every post?
- tomrod 4y agoUnder the rule that identifies meta discussions are inevitable regarding no JS posts ;-)
- reaperducer 4y agoWhere is the rule that people need to complain about JavaScript at least once for every post? It's there, but you can't see it because the rule requires JavaScript to view the rule.
- 9wzYQbTYsAIc 4y agoI believe that the rule is WOULD PROBABLY according to RFC 6919 [1] but it MIGHT be MAY WISH TO? [1] https://www.rfc-editor.org/rfc/rfc6919#section-5 https://www.rfc-editor.org/rfc/rfc6919#section-5
- dylan604 4y agoBut in this case, it is a decent question. Why is it not called MetalliJS? It's not CSS so much that you can just open up a CSS file and manipulate it. You have to dive into a JS file to modify CSS? That's not intuitive at all. It just seems a very strange way of going about demoing a CSS library.
- toastal 4y agoIt's about the experience. Having JavaScript is fine, but <noscript> is a part of accessibility. It's just plain broken with no warning when scripts are disabled. It's a wise practice to personally disable scripts by default with an add-on and only opt yourself into scripts as needed--for privacy, for security, saving bandwidth. In this specific case, one should be able to view the default demo without JS because it's a CSS library/demo and not a JS one. You can (and should) progressively enhance it with JS.