A conspiracy to kill IE6 (2019)

Post by stephen_g » Thu, Feb 08, 2024, 6:03 AM UTC

jwells89 wrote: post #38

ksherlock wrote: post #31

Earlier quoted context omitted.

The thing about IE, one thing anyway, is that it's CSS support, box model, etc, was broken and non standard. So you would need to exploit CSS parser bugs to give IE a separate CSS, use DXImageTransformFilter to make png transparency work, etc. Maybe by WebKit you mean Blink and by Blink you mean V8, because when somebody does a "Show HN: something that doesn't work in Safari or FireFox" it's usually a javascript prob…

That DirectX filter hack for PNG transparency haunts me. What makes it so much worse is that Tasman, the engine used in IE for Mac, had awesome support for CSS, transparent PNGs, and more years earlier, but for some reason it got dumpstered when IE for Mac was discontinued while the inferior Trident lived on in Windows.

Post by matwood » Thu, Feb 08, 2024, 7:25 AM UTC

ttfkam wrote: post #40

ksherlock wrote: post #31

Earlier quoted context omitted.

The thing about IE, one thing anyway, is that it's CSS support, box model, etc, was broken and non standard. So you would need to exploit CSS parser bugs to give IE a separate CSS, use DXImageTransformFilter to make png transparency work, etc. Maybe by WebKit you mean Blink and by Blink you mean V8, because when somebody does a "Show HN: something that doesn't work in Safari or FireFox" it's usually a javascript prob…

I came to hate IE with every fiber of my being, but let's call a spade a spade here: IE basically invented modern CSS. Netscape 3/4 and IE 3/4 had very different views on how web pages should be dynamic and how they should be styled. IE championed CSS and the DOM. Netscape was fixated on bgcolor, font tags, etc. Netscape introduced the tag. IE just made every tag a potential layer. Remember AJAX? Loading content from…

Post by realusername » Thu, Feb 08, 2024, 7:35 AM UTC

tannerellen wrote: post #74

jimmaswell wrote: post #54

Earlier quoted context omitted.

Safari is the one and only browser I continue to need to write special extra CSS for.

This is a red flag that you are trying to use non standard CSS or you are trying to use things that are so bleeding edge that you are requiring even evergreen browsers to have been restarted and updated very recently. Set your target to any CSS that has been around for about a year or so and is based on standards and you shouldn't need to be writing anything different for specific browsers. I haven't had to target a…

Post by al_borland » Thu, Feb 08, 2024, 8:38 AM UTC

ozim wrote: post #90

cogman10 wrote: post #4

One of the best things that's happened to the web is all browsers moving over to an evergreen model of distribution. IE was such a cancer on the internet, everyone in the bad old days programmed to the lowest common denominator (IE6, 7, or 8). Even while brand new features and standards were widely adopted by everyone else. One of the worst things that's happened is nearly everyone converging on using webkit to rende…

Browser engine for me is like a Linux kernel for me. Everyone should be banding together to work on one. Not making a separate one each year. We have js libraries and frameworks for that. Of course some innovations that requires to be done in engine won’t happen as fast - but on the other hand amount of innovation in software that runs in browsers will be much higher. We saw that with IE “innovations” of Microsoft bl…

Post by arielcostas » Thu, Feb 08, 2024, 8:45 AM UTC

tempestn wrote: post #76

The thing that gets me the most is how ancient 10 year-old YouTube looks. Which makes sense that this was the era before smartphones, when IE6 still had significant market share. But 10 years! Sounds like such a short time.