Lea Verou joins W3C


Working at W3C had been a dream of mine ever since I learned what a web standard is. As you probably know if you’ve been following my work, I’m a strong believer in open web standards. Even though proprietary technology might offer some short term benefits, in the long run only open standards can allow the Web to reach its full potential.

The web is in good hands!

Mass-unprefixing in Firefox 16

Paul Rouget:

In Firefox 16, we are unprefixing:

  • CSS3 Animations
  • CSS3 Transitions
  • CSS3 Transforms
  • CSS3 Gradients
  • IndexedDB

Also calc() might be unprefixed as well if time permits.

The Firefox team have been working hard!

iOS has a :hover problem

Nicholas C. Zakas:

So don’t believe people when they tell you that hover doesn’t exist on touch devices. At least on iOS, hover does exist and needs to be planned for accordingly. If you are using a :hover rule to show something in your interface, you may want to hide that rule when serving your page to a touch device. It might be a good idea to just completely remove all :hover rules for any experience that’s going to be served to a touch device. The touch-based world doesn’t need hover, so be careful not to inject it accidentally.

Idiomatic CSS

Principles of writing consistent, idiomatic CSS. The days of a simple web page seem to be long gone for me so reading documents and adopting the best practices are a must to improve as a developer. This document is in its early days and will no-doubt evolve and become a “go-to” source.

The document is broken down into 8 sections:

  • General principles
  • Whitespace
  • Comments
  • Format
  • Naming
  • Practical example
  • Organization
  • Build and deployment

Each section is explained very clearly and the practical example ties all the explained styles/patterns into one very simple example.

If you are a passionate developer and don’t have a consistent styles/patterns when writing your code then head over to the Idiomatic CSS document on GitHub and maybe try to adopt some of the principles into your current or future projects.

“Part of being a good steward to a successful project is realizing that writing code for yourself is a Bad Idea™. If thousands of people are using your code, then write your code for maximum clarity, not your personal preference of how to get clever within the spec.”

– Idan Gazit

Responsive Workflow

Viljami Salminen, a UI/Web Designer and Developer from Finland explains his responsive workflow. He offers some great thoughtful descriptions on each individual step. His responsive workflow is broken down into the following steps:

Discover, Plan, Text Design, Sketch, Prototype, Visual Design, Test, Discuss and Iterate.

Some highlights included the free ‘Device Breakpoint Diagram’, the Text Design step (which was a new concept to me) and the Visual Design step which included some great typography tips.

‘Text design’ here means that we write (design) all the contents of the website down in textual form. This is one of the most important stages in the whole process, and yet it’s probably also the most underrated step.

Visual design. This step happens in iterations before and after prototyping. I still use Photoshop to do most of the design, but I’m moving more and more towards design in a browser. Especially typography seems to be something which is really hard to get working anywhere else than inside the browser (Although at the same time I have noticed that if I do the jump too early, everything will end up looking flat, uninspiring and somehow cluttered).

Sass vs. Less

Chris Coyier covers the hot topic of “Which CSS preprocessor language should I choose?”. He does a great side-by-side comparison. It is a great read if you are already using CSS preprocessors or not. Also be sure to check out the 160+ comments!