> Everything you've said throughout this thread is a series of highly opinionated, subjective rationalizations. They are, but they are opinions based on a deca

> Everything you've said throughout this thread is a series of highly opinionated, subjective rationalizations. They are, but they are opinions based on a decade and a half of working with these technologies, and being currently employed as a specialist in responsive CSS. I'm not just giving you my opinions, I've been linking directly to open-source solutions I get paid to provide for clients. No pitch, I've done the opposite—I've given you the jewels. You won't need to hire me to fix these things now if you use my code for free ;) > Yet you continue to deliver these rationalizations as if they're incontrovertible facts. Based on hundreds of hours of testing across different browsers and devices, you're going to have to trust me that what I have left is thoroughly tested and proven to work. I have nothing to gain or lose from what I've said here, but some of the insight and code samples I've provided might help people avoid or fix a whole class of common website bugs - the kind that are hard to reproduce, and hard to test because they usually pop up on exotic hardware or software configurations. I Hope my opinions, tested code, and experience have helped some professionals in this thread :) I'm curious how you would approach building a website that isn't broken when viewed on dozens of devices and browsers. Do you have any opinions, code, or suggestions to contribute to the discussion?