Jeremy Keith’s recent post Polyfills and products asked an interesting question about handing polyfilled code to clients:
[Short term client projects] makes it very tricky to include a polyfill in our deliverables. We’d need to figure out a way of also including a timeline for revisiting that polyfill and evaluating when it’s time to drop it.
I presented an expanded version of my CSS Naming Conventions talk at WordCamp Sydney. Thanks to everyone who came along, my slides are below.
I’ve put together a quick one page site linking to various resources at cssnamingconventions.com.
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. (more…)
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. (more…)
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.
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
}