12 posts filed under Cross-Browser Compatibility, newest first.
The popover attribute gave me the top layer last spring and left me doing all the math, and the CSS that finishes the job has landed in one browser and deletes a positioning library, 2 scroll listeners and a resize observer.
A client circled three buttons in a screenshot and asked why one of them sat lower than the other two, and the answer was a hole in Grid I complained about six years ago and then stopped noticing.
A client asked whether the newsletter could look like their new site, which is a completely fair question, and answering it honestly meant explaining that the biggest email client in the working world lays out HTML with a word processor.
A card came out with its heading jammed against the top border, because the class that says a card has no image gets added by a template, and the template rendering that particular row had never been told to add it.
A screenshot arrived six weeks into a build and nothing anywhere in the project said whether we supported that browser, so whether it counted as a defect got settled by whoever happened to be standing in the corridor.
A page on two bars doesn't fail, it just sits there, and that turned out to be the only state where the thing I spent an evening building does anybody any good.
Most of what jQuery was invented to fix has been fixed in the browsers, and a lot of us are still loading the whole library to avoid typing a slightly longer method name.
Browser support looks like a technical decision and gets argued as one, but it's a commercial decision with a number attached, and the number is usually available if you go and ask for it.
Flexbox has crossed the line where I can use it on real work, and the surprise isn't the layouts it enables. It's how much of my CSS turns out to have been compensation for not having it.
Div soup is what you write before you learn what the other hundred elements are for. The argument for fixing it isn't screenreaders or SEO, it's the next person who opens the file.
Every browser has picked a different answer to what should happen while a web font downloads, and all of the answers are bad so the decision quietly falls to you whether you choose to make it or not.
We are building every grid on the web out of a property invented to wrap text around a picture, and the pile of workarounds we've grown on top of it has stopped looking like workarounds.