Stephen Caver
I’ll Take Both, Please

Eric Meyer brings up an interesting philosophical conundrum in his post Rounding Off about font-size rounding and the computed values web inspectors report to developers.

Go ahead and read the whole thing and come back, I’ll wait.

So, first of all, Eric’s brilliance for even presenting this issue is undisputed. However, he poses a question at the end of his post:

What do you think? Should web inspectors report the CSS computed values accurately, without regard to the actual rendering effects; or should the inspectors modify the reported values to more accurately reflect the visual rendering, thus obscuring the raw computed values

Well, very kind of you to ask, Eric. My take, is yes. I want both.

I think this is helpful in a few ways. First, knowing how browsers are interpreting values is important in writing robust, accurate stylesheets. If you’ve ever been scratching your head why that bit of typography looks a pixel or two smaller in Firefox as it does Safari then you understand what I mean.

Knowing the effective display size is important in determining how accurately the rendered design reflects designer mock-ups. Or, if you’re designing straight in the browser, making decisions on size ratios, leading and other important typographic details that are relative to the size of the type.

I didn’t do any heavy thinking or analysis on this matter, so in fair warning I could even be misunderstanding Eric’s question. But my initial thoughts are to ask why not both? And hey, it certainly felt good to do a bit of off-the-cuff writing.

An age old question of the web designers world.

CSS gradients in practice.

Very welcome news regarding IE9.

Textmate solved this problem for me a long time ago. With a simple hotkey I can see all the selectors on a single line or all the properties on their own line. Best of both worlds.

A look into the future of web design.

Excellent!

text-rendering: optimizeLegibility;

Research on typography as it relates to CSS from the fine folks at TypeKit.

There are definitely pitfalls with media queries that make them less than ideal for mobile websites. The New York Times is probably not going to want to use it as a major part of their mobile strategy. That said—and I wish Mr. Grigsby hadn’t spent an entire article trashing media queries before ceding this point at the very end—Responsive Web Design and media queries are ideal for designing desktop websites and breaking the tyranny of 960 pixels wide.

A CSS3 case study from Dan Cederholm.

Noah Stokes breaks down CSS positioning. Recommended reading even if you think you have all this stuff down.

Not necessarily required reading, but interesting.

Chris Coyier experiments with creating shapes using CSS.