[CaptainOfCoit]

I remember many similar cycles of having different browsers open side-by-side, and trying to pinpoint (without the developer tools we know and love today) the exact reason why one border was one pixel in one browser, and two pixels in the other, throwing the whole layout off.

Also remembering when Firebug for Firefox appeared, and made so many things so much easier. Suddenly things that took hours took days, and it was so much easier when you had some introspection tools.

[yard2010]

* { border: red 1px solid } Remember when IE6 was a thing? The kids today are angry at chrome for good reasons and yet, there was a time in which the most popular browser didn't implement jack shit from the specs. And it was the kind of browser that ships with the OS.

God the bad karma for working with this crap. I'm glad it's over.

[hinkley]

I had to do a reflow reordering trick on a sibling page in that app and it doubled or tripled the speed on FF and safari, but on IE6 the test case went from 30s to 3.5s. Good Christ.

[hinkley]

That bug took me on a whirlwind tour of that code and I understand why they wanted to start over. Woof.

[tosapple]

>> and made so many things so much easier. >> Suddenly things that took hours took days

Inverse? Shouldn't it be things that took days took hours ?