The difference between and is easy to overlook. It seems to be one of those things that falls into the category of trivial. Admittedly, I have a bad habit of applying all global styles to and, when that falls short, I move to without thinking about it.
Welcome to THE ultimate resource for creatives. Up-to-the-minute updates from over 180 of your favorite design/dev/photo blogs around the web, all in one place... Stay a while!
We also contribute our own content to the design community. View our Original Posts.
I don't particularly like clothes shopping. So I don't. 95% of the clothes I own I buy online. But I also like nicely made clothes. It's not a splurge. They last longer, are more comfortable, and end up being a more economical buy.
Matt Gaunt shares that IE 10 and bleeding edge Chrome and Opera how support document.execCommand('copy'); and friends, which can make for some mighty convenience UX opportunities.
The following a guest post by Andi Dysart and Matthias Christen of Ghostlab. I was pretty impressed when I heard that the newly-released Ghostlab 2 could do this. I think a lot of us developers use Chrome because the DevTools are so good, and it sure would be able to use them in other browsers, even on mobile devices. And why not? Chrome DevTools are a part of Blink, which is open source, right? We just needed a tool …
Marie Mosley just finished up a revamping of the text-decoration property (and friends) in the Almanac. You're probably aware of this property. For instance, most default browser styles include underlined links by way of text-decoration: underline; - which you can remove with text-decoration: none;.
We put up a proper Team page. CSS-Tricks isn't just me, but a whole team of part-time staff that keep this ship sailing. That includes writers. We've always had guest posts, but now, for the first time, you'll be seeing articles not written by me that also aren't "guest" posts, because they work here! Example. Notice it doesn't have an introduction written by me like a guest post would. We'll get proper author archives up soon.
The concept behind the will-change property is to stop using hacks like transform: translateZ(0) to tell browsers where to optimize and standardize it. The typical, understandable gripe is that this complicates CSS. Shouldn't browsers be smart enough to do these optimizations, rather than leaving it up to us authors? To which browsers say: it's near impossible to heuristically determine these things. Much like the sizes property in responsive images - just telling the browser allows it to act on
A reader wrote in explaining their problem with the process at work. I'm posting the question and my response here, with permission.
Many emails are designed with a large screen in mind. Text that looks great on a large screen can be difficult to read on a mobile device, though. If Gmail deems that the font-size of any text in an email is too small to be legible, it will increase the size and flag the message. That’s pretty nice. What could have been illegible is made legible, eliminating the need to pinch and zoom our screens.
It's a new web project. You're starting from scratch. The front end is going to be clean and orderly. You've set your defaults. Your CSS files are organized. You've got a system! This time will be different. What could possibly go wrong?
If you don't share experience with others, your effectiveness will never scale beyond your own efforts. If you impart your battle scars on others without considering the circumstances in which they were inflicted, people who believe you will miss out on awesome things. The challenge of the experienced developer is to pass on wisdom without passing on dogma, but most developers think their personal experience should be enshrined as a best practice.
I don't know about you, but I sure like the idea of celebrating the good to balance out all the shaming of the bad.
The following is a collaborative post by guest Joe Richardson, Robin Rendle, and a bunch of the CSS-Tricks staff. Joe wanted to do a post about BEM, which we loved, and just about everybody around here had thoughts and opinions about BEM, so we figured we'd all get together on it and do it together.
My anecdotal evidence regarding CSS selector performance is: I've never once bothered with optimizing for it, and typically outright ignore traditional "advice" around it, and it's never been a problem.
But there are some situations where you want to defer loading of CSS - for instance a stylesheet of custom fonts you don't mind downloading late. Or even your main stylesheet if you're doing critical CSS.