There is a CSS bug.
CSS bugs are dirt common. It's a miracle that there are as few CSS bugs as there are. However, I remember IE6. IE6 was a total fucking mess. Everything was broken on IE6. It wasn't just a bug, it was a complete support nightmare.
I routinely encounter problems with CSS that reveal maddening differences between Chrome, Firefox, and Safari. That's just for desktop. But it's still way better than dealing with IE6.
Indeed. While Safari does have its problems, it is a long, long way from being as bad as IE used to be. I recall one project where making it work on IE required that about 30% of the code be rewritten.
Then the time card website upgrade, which only worked in ie.
So now log onto Unix, use a VPN (Citrix) to log onto a windows NT machine, then use IE. It had to be done daily and wasn’t fun.
Most competing browsers chose to implement IE6 rendering (border box model, quirksmode etc), bug-by-bug. To at least have some of those "built for ie6 only" websites functioning and looking OKish.
But when those quirks would break the website on anything but IE6, many webmasters (is that still a function-title in 2021?) would not care, or not get budget to fix it: "96% of our users use IE6, why spend time for those 4%?". (which also begs the question: what are those 4% doing on a website that doesn't work at all for them? Shouldn't that be 100%/0%)
But still, most CSS bugs aren’t so severe.
I knew it'd be this number right away, because it's also the maximum screenshot height thanks to being the maximum height of a surface in Chromium (Actually last I checked this technically depends on the GL backend used, but 16kpx seems common)
Back in 2000, I was living in a new city, and cold-calling graphic design firms. At the time, most of the web looked like utter ass, and my feeling was that it made more sense to try to be the in-house developer for designers, rather than try to bring design to web development firms.
So I put together a resume with my personal URL placed prominently across the top, and knocked on the door of every graphic design firm in Portland. I met a bunch of confused designers, and didn’t get a single call or email back. I noticed in passing — and importantly to this story — that the whole industry was still wedded to Macs running the non-memory-protected OS 8. Months passed and my savings trickled away.
Eventually out of desperation I took a job at a shipping company that was rewriting their in-house software suite. I noticed that they had a couple dusty Macs in the corner for browser testing that they never bothered doing, and thought it might be amusing to see how my site loaded.
It turned out that there was an error in the CSS engine in MSIE Mac that crashed the system. Not the browser, the entire computer. Click, smash. I realized with horror that I had spent months crashing the computers — along with the unsaved work — of every graphic designer in Portland.
On some computers without enough memory the "fix" crashed the entire OS with a bluescreen (no idea what the bug was because I didn't have windows, and because... well it's windows, I think I developed it in WINE!). I only found this out through a client complaining about their clients computers bluescreening when visiting their site... this was probably 2008-ish, so not exactly peak IE6, but it was the phase where a bunch of orgs still forced everyone to use it under the ridiculous premise of "security".
We were pretty much stuffed due to depending on iframes. Some users are stuck on that version of iOS because their device is "too old" for Apple's liking and we have to tell those users we can't support it, which is horrible because we are effectively being used by Apple to coerce those users to throw their devices away...