The recent release of Firefox 31 brought an implementation of CSS Variables. Based on that, Daniel Imms wrote an interesting post, What CSS Variables Can Do That Preprocessors Can’t, where he investigates a few use cases for native variables over those provided by pre-processors like Sass and LESS (there’s a common argument that CSS variables …
Some UX Lessons - For FREE!
UX Lesson #1: A username is a username, an email address is an email address. An email address is NOT a username. Stop calling it that, retards. If you’re going to use users’ email addresses as logins, stop labeling it “Username”.
UX Lesson #2: On login, tell users which field is incorrect. “That password is incorrect,” or “That username does not exist”. And if the password is incorrect, don’t clear the username field so they have to enter it twice.
UX Lesson #3: If you do one of these, fix it immediately. If you do both of these, punch yourself in the face. And then fix it immediately.
Simplicity is not the goal. It is the by-product of a good idea and modest expectations.
Simon And Garfunkel’s ‘The Sound Of Silence’ On Floppy Drives and HDDs
Increase Browser’s Performance Tip
When setting an element’s position to fixed, make sure you add to the CSS class the following attribute: backface-visibility: hidden; (don’t forget to add the provider’s prefix. e.g. -webkit-, -o- etc) or translate3d(0, 0, 0); This will prevent browser re-painting it on scroll and hence increase performance.
Increase Browser’s Performance Tip #2
Always prefer css
opacity: .5since with filters, some browsers provide hardware acceleration for better performance.