There are a few Sass media query mixins going around for dealing with old versions of IE. Often they include predefined break points, whereas I like the simplicity of passing a numeric value.
Capable browsers wrap the content in a media query, incapable browsers get the unwrapped content.
I had the pleasure of speaking at Be Responsive Melbourne last month on the subject of CSS Naming Conventions.
Both my slides and the video from the evening are now available.
I’ll be speaking at Web Directions’ What Do You Know Melbourne — The Smackdown Edition on August 27. You should come along.
There will be eight speakers debating four topics for five minutes each. Plenty of variety without going on too long. I’ll be arguing RWD is better than an m-dot site.
There is talk of requiring Australian ISPs collect & store metadata as a user browses the net. Metadata can include a lot of information, for example this is what’s included in a single tweet
I’ve imported my posts from 2011 and earlier from their old home at Big Red Tin.
Some of them need a little tidying up to point internal links to the correct location, others need to be tagged as obsolete (fallbacks for CSS rounded corners anyone).
It’s been interesting going back and reading some of my old pieces. Although my methods have changed, there’s a good number that I still hold to be true; the importance of !important is one such post.
As I’ve mentioned previously, I’m in the process of redesigning this web site. It’s very much a work in progress.
As a first step I’m building a pattern library and I’ve decided to open source the repo during the build process. I’m using Pattern Lab for the purpose.
The MDN page titled Sections and Outlines of an HTML5 Document includes the following warning:
There are currently no known implementations of the outline algorithm in graphical browsers or assistive technology user agents […] authors are advised to use heading rank (
h1–h6).
Given the speed at which CSS3 is implemented, this is disappointing. Visitors to this site use modern, capable browsers; it’s a shame not to be able to use the most logical document outline.
For years, Firefox has taken the prize for the single most frustrating rule in a UA stylesheet.
input {
line-height: normal !important
}In my last post, I mentioned I was trialling the SUIT CSS naming convention as I redevelop this site. More generically, let’s address why a naming convention should be used at all.
For the purposes of this post, I’m talking specifically about class naming conventions. (While one may have naming conventions for JavaScript functions, variables, and HTML IDs too, they’re not the focus of this post.)
I’m in the process of redeveloping this site. The site will still use WordPress but I’ll be adding a custom skin.
I’ve been wanting to try Pattern Lab for a while, so the first step is to create a pattern library. It’s early days, today’s task it to set up a reset and base styles.
Additionally, I’ll be sampling a CSS naming convention I’ve been meaning to try for a little while. A personal project is the perfect opportunity.