<button>Let's Go !</button>| // localStorage example | |
| var hasStorage = (function () { | |
| try { | |
| localStorage.setItem(mod, mod); | |
| localStorage.removeItem(mod); | |
| return true; | |
| } catch (exception) { | |
| return false; | |
| } | |
| }()); |
| (function() { | |
| "use strict"; | |
| setTimeout(glitch, Math.random() * 3e5); | |
| function col() { | |
| return '#' + (Math.random() * 100).toString(16).slice(-3) | |
| } | |
| function glitch() { | |
| var n = Math.floor(Math.random() * 4 + 4); |
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
