For some reason, I seem to have a fascination with CSS loaders these days. After recreating the Google loader with clean CSS recently, I set off to recreate the classic spinner with CSS. Yes, I know this has been done zillions of times, but I wanted a clean, maintainable, reusable solution, not just a proof of concept. Something with not tons of CSS and/or HTML elements.
Very nice, simple and clean solution building a CSS only spinner.
ResponsiveComments was designed to bring simple conditional loading to the client side. Although not the complete answer to conditional loading in responsive web design, ResponsiveComments provides a solution to simple conditional loading, directly within your markup, using HTML comments, media queries and feature detection.
This year, it should be no surprise that people use mobile devices to buy things online. But when you compare this years early holiday shopping numbers with last year, the growth actually is pretty surprising.
Just in case anybody needs to be convinced that responsive Design is more than just a side-feature of a website.
This is what the Mozilla community is all about — championing a web where people know more and do more, a web that they can make their own and use to make their lives better.
As I’ve said a few times in the past already, I love what Mozilla and Firefox stand for and I appreciate what they do, but more often than not their products are not as good as the ones from others and that makes it hard for me to use or to support them. And that in turn makes me kinda sad.
The fact that Blink is apparently calling src-N dead in the water because one implementor opposes (WebKit) and yet haven’t said the same about srcset which is also opposed by an implementor (Mozilla) speaks volumes to the rationale here: it’s not because there isn’t a consensus, it’s because of who is wielding the heavier stick. The fact that the RICG have thrown their support behind src-N appears to not really figure into the equation.
So here we are 21 months after the RICG was started. We finally have a solution that both the RICG and a majority of implementors are interested in, and it looks like it’s at risk of not happening because of one single implementor dissenting opinion. The fact that the currently discussed solution on the WHATWG list is a frankenstein combination of HTML and inline CSS doesn’t do much to elevate my spirits
True words by Tim Kadlec on the responsive images solution or should I say debacle? Go read it, now.
You probably build websites and think your shit is special. You think your 13 megabyte paralax-ative home page is going to get you some fucking Awwward banner you can glue to the top corner of your site. You think your 40-pound jQuery file and 83 polyfills give IE7 a boner because it finally has box-shadow. Wrong, motherfucker. Let me describe your perfect-ass website
I’m probably the last one linking to this, but it’s so good. :D
I designed our new layouts this time not by working ‘mobile first’ but ‘tablet first’ and my iPad mini, now retina, became my ‘control’ device. Everything about the new design has been made to look its best on a retina iPad.
The new ‘Stuff and Nonsense’ looks really really good. Solid responsive work with some nice easter eggs here and there. And as Andrew, I love the Typeface they’ve chosen.
Basically, I want to be given a random browser’s rendering of my page every time I refresh the page.
I think this is a great idea. Even though I’d like to have an option (maybe ALT + CMD + R) to refresh with the same engine if I’m about to fix a bug and want to see if I did good.
All we have to do is add the .disable-hover class to the body when the user begins to scroll. This then allows the users cursor to pass through the body and thus disable any hover effects.
Wonderful little script and technique to improve frame rates on websites while scrolling. Hitting 60fps should always be our goal.
Markdown has arrived on WordPress.com!
Finally! I hope it’ll land in the self hosted version of WordPress, too. I used many different Markdown plugins but everyone had some kind of flaw.
Again, my primary goal for this little pink book is to simply get more people interested in using Sass to make their lives easier. Sass is a wonderfully helpful tool with a great community behind it, in a discipline that can be complicated and frustrating. I’m hoping you give Sass, and the book, a try!
Another book by Dan Cederholm is out since a few days. I haven’t read it, but I’m sure it’s a great one and with the high quality we know of Dan. If you want to get into Sass and don’t know how, this book will be a great fit for you.