Missing the whole IE quirks mode vs standards mode thing, but nice.
Some of those hacks were specifically for IE, and there was a debate on staying quirks vs going standards mode. Each had its own drawbacks and choices.
I used these CSS styles in the late 90s to make internal browser-based apps for our call centre agents that looked & felt more like native Windows desktop apps.
The really funky part of the IE6 PNG fix was that the URL of the image in the expression was always relative to the current page URL, not the CSS file that the declaration was in.
I remember having to use Javascript to generate the image path (I cannot quite remember why absolute or root-relative URLs were not an option for us though...)
I was having a peaceful day until these CSS curiosities brought back memories of my painful days. It's really good that we don't need to deal with such hacks and vendor-specific things anymore. The last time I participated in a project that targeted an old browser was in 2018!
The magnitude might be greater in specific sub areas, for example if you are doing chrome first, how is your accessibility on Safari? I don't know myself, but I think there are holes people don't notice with this approach.
Also I agree the thing about Meerita's post being flagged and dead seems wrong. There is evidently nothing wrong with the post and it should not be.
Mostly Internet Explorer 7 and 8, some Mozilla Firefox builds. That’s what I had in mind when I said “old browsers.” The last project I worked on that still had to support browsers from that era was in 2018.
Sounds about right. Looking back I’d already moved IE7 to “functional” support in late 2016[1] and was planning to do the same to 8 and 9 in the not too distant future.
it was frustrating but i preferred it to dealing with stuff like node, tooling, mobile and tablet views, that stuff really burned me out in a way that IE 6 never did.
Some of those hacks were specifically for IE, and there was a debate on staying quirks vs going standards mode. Each had its own drawbacks and choices.
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/V...
I used these CSS styles in the late 90s to make internal browser-based apps for our call centre agents that looked & felt more like native Windows desktop apps.
I remember having to use Javascript to generate the image path (I cannot quite remember why absolute or root-relative URLs were not an option for us though...)
Unfortunately that means everyone targets chrome.
Then you end up with shit performance or broken sites in Firefox [1].
You'd think with "AI" they could generate js/css that works in both browsers...
[1] Which is the only browser that can still run proper ublock origin...
Edit: someone pointed below that the compatibility problem's magnitude is much smaller. Seems flagged and dead for unknown reasons.
The magnitude is probably much smaller, but that makes it worse, because people will just forget about FF.
Also I agree the thing about Meerita's post being flagged and dead seems wrong. There is evidently nothing wrong with the post and it should not be.
[1] https://technology.blog.gov.uk/2016/10/21/gaining-understand...
I wonder how many collective years of developers’ lifespans were dedicated just to addressing its quirks.
i was seen as a genius at work for understanding quirks mode and how JScript differed from javascript/ecmascript