What I do want to put the focus on, however, is that you have to perform an audit of your product every so often and see how the people using your product have changed, and what kind of functionality that made sense at the time may not make much sense anymore.
And herein lies the problem with developers having control: we’re guessing based on the information we’ve got. Today we base our guesses on screen size; but when these media queries come in we’d be guessing based on pointer accuracy and hover capability… which is better but still not ideal, because it doesn’t tell the whole story. So do we need even more media features to get the level of control we need?
Through the years, this lack of detail in the CSS specification has forced Web developers to produce a significant number of tests and examples whose primary goal is to reduce form elements to a common visual denominator in order to get a cross-browser rendering of elements such as input, select, fieldset, legend and textarea. In this article, we will cover some of the CSS patterns used by Web developers to tame the visual layout of form elements.
In summary, most people reading text on the web view type in one of these five ways. Mac OS X users see Core Text, Windows 7 and Windows Vista users see either DirectWrite or GDI, and Windows XP users see GDI.
§Rollbar just launched out of beta. We migrated over from AirBrake a couple of months back, and it works like a charm (we do Node and Ruby). Better error messages, daily summary, multiple logging levels, and more. Recommended.