IE6 had major compatibility bugs that were never going to be fixed. For example:

* It considered width to include border and padding, when the spec and other browsers did not: https://www.jefftk.com/p/the-revenge-of-the-ie-box-model

* Floated block elements would get their margins doubled, so people would typically use padding instead.

* Its implementation of height was more like min-height.

While I'm sure Firefox and Chrome have open bugs that are older than that, I'd expect them to be much less important than these critical misinterpretations of CSS.

Well, I can track down examples of similar critical bugs for Chrome, but then again, I guess it would just move the goal posts to another defence round for Chrome.

You think Chrome, Firefox, Edge, or Safari (the main evergreen browsers) have bugs that have been open for years and are as critical as considering an element's width to include its border and padding? This misinterpretation of the CSS specification was something that essentially all front-end developers had to work around for 10+ years!

Yes I think so, all of them have bugs that web developers have to work around, again should we look at Chrome's bug database or maybe AdWords has a better source of information for such workarounds?

If you want to point to an example bug, I think that would help me understand your point, yes.

(To give a sense a sense of the scale I think we're talking about, this would be a bug that, say, more than half of web developers have to understand and work around in a typical month)

My point it that you are tainted by your employer, so this discussion is worthless, no matter what I come up with.