3 ms·

I use IE6 as a sort of litmus test for websites. If a site works in IE6, it's more likely to work on every browser imaginable. Those people creating sites desig

I use IE6 as a sort of litmus test for websites. If a site works in IE6, it's more likely to work on every browser imaginable. Those people creating sites designed to work in the latest browser version only scare me to death.

w-j-w 5y ago
The landscape has changed. Most typical, everyday user have browsers that update themselves to the latest version. Supporting ancient technology (like IE6) doesn't provide a benefit that really justifies the enormous amount of work required. Just let the old browsers die already.
labster 5y ago
Flexbox and block-scoped variables aren’t really that scary. Honestly less scary than the alternatives, nested tables and global variables. Sometimes it’s okay to have nice things.
- asddubs 5y ago
  ie6 doesn't even have inline-blocks. now that's scary
resoluteteeth 5y ago
If you mean that IE6 represents some common set of baseline features that all other browsers will support this is absolutely 100% false. IE6 has tons of quirks and nonstandard features, and sites that are truly written specifically for IE6 and target its features (e.g. activex) and numerous css bugs will simply not work or display correctly in any other browsers at all. Newer versions of IE have to have two separate rendering modes. One of these, "quirks mode," is a non-standard mode that specifically emulates the broken IE6 functionality, because this is the only way to correctly display pages designed for IE6 in a modern browser. On the other hand, people writing new sites in 2021 that support IE are people who are very concerned with compatibility who are being very careful and using zillions of LOC of pollyfills to ensure the sites work in IE. The sites these people create will work in other browsers not because of any property of IE6, but because the people making them also put a lot of work into ensuring they are compatible with other browsers, and dropping support for IE would save a lot of work without reducing compatibility with other browsers.
onion2k 5y ago
If a website still works in IE6 then there are some serious problems with the site's security implementation. IE6 doesn't support TLS 1.2 or 1.3, it's vulnerable to POODLE, RC4 and FREAK attacks, and there's no ECC compatibility on any OS. If a site loads in IE6 stay the hell away from it.
- CodesInChaos 5y ago
  As long as there is no protocol downgrade attack, server support for TLS 1.1 in addition to 1.2 won't affect people using modern browsers.
- ______- 5y ago
  I would have my site on a local staging server that uses HTTP before I push it to production where HTTPS/TLS would be turned on.

w-j-w 5y ago

The landscape has changed. Most typical, everyday user have browsers that update themselves to the latest version. Supporting ancient technology (like IE6) doesn't provide a benefit that really justifies the enormous amount of work required. Just let the old browsers die already.

labster 5y ago

Flexbox and block-scoped variables aren’t really that scary. Honestly less scary than the alternatives, nested tables and global variables. Sometimes it’s okay to have nice things.

asddubs 5y ago
ie6 doesn't even have inline-blocks. now that's scary

resoluteteeth 5y ago

If you mean that IE6 represents some common set of baseline features that all other browsers will support this is absolutely 100% false. IE6 has tons of quirks and nonstandard features, and sites that are truly written specifically for IE6 and target its features (e.g. activex) and numerous css bugs will simply not work or display correctly in any other browsers at all. Newer versions of IE have to have two separate rendering modes. One of these, "quirks mode," is a non-standard mode that specifically emulates the broken IE6 functionality, because this is the only way to correctly display pages designed for IE6 in a modern browser. On the other hand, people writing new sites in 2021 that support IE are people who are very concerned with compatibility who are being very careful and using zillions of LOC of pollyfills to ensure the sites work in IE. The sites these people create will work in other browsers not because of any property of IE6, but because the people making them also put a lot of work into ensuring they are compatible with other browsers, and dropping support for IE would save a lot of work without reducing compatibility with other browsers.

onion2k 5y ago

If a website still works in IE6 then there are some serious problems with the site's security implementation. IE6 doesn't support TLS 1.2 or 1.3, it's vulnerable to POODLE, RC4 and FREAK attacks, and there's no ECC compatibility on any OS. If a site loads in IE6 stay the hell away from it.

CodesInChaos 5y ago
As long as there is no protocol downgrade attack, server support for TLS 1.1 in addition to 1.2 won't affect people using modern browsers.
______- 5y ago
I would have my site on a local staging server that uses HTTP before I push it to production where HTTPS/TLS would be turned on.