We dropped support for Internet Explorer!

This was a +92 -10,723 diff!

There had been support down to IE6...

https://github.com/python/pythondotorg/pull/2856

#Python #InternetExplorer #IE6 #IE7 #IE8 #IE

Today I have been updating (not paying!!) a Struts 1 app with Internet Explorer 6 compatible JavaScript to work on modern browsers. This continues tomorrow, and probably for a few days more. Wish me luck!!

#ie6 #java #javascript #legacyupgrades

@gordoooo_z @rl_dane well, #FrontendDevs like @fuchsiii get a kilometer stare.when you ask her to support #IE6!

#Glasfaser ist die #Zukunft ! #FTTH #Neuland #IE6

A Conspiracy to Kill IE6 (2019)

https://blog.chriszacharias.com/a-conspiracy-to-kill-ie6

#HackerNews #ConspiracyToKillIE6 #IE6 #Death #2019 #WebDevelopment #BrowserWars #TechHistory

Gosh darn it #Safari really is the IE6 of 2025...

#iOS #MacOS #Apple #IE #Ie6

Yes, it's that bad

La guerre contre #ie6 n'est jamais terminée :(

Vivement #servo

"Go home, IE6!" "I can't believe you're related to that guy, IE7."

#software #InternetExplorer #WebBrowsers #IE6 #IE7 #art #funny

Methinks, Microsoft public celebration of #IE6 demise is all about the prowess of their newer generation browsers. #WebID #Security #Privacy

@shaknais #InternetExplorer is #EoL anyway, so disregard it.

• Unless you are a masochistic #WebDev, then please, go on and backport stuff to #IE6 & #WindowsXP on the #InternetExploder!

In AU, 3.2% still uses #IE6 #ie6countdown http://bit.ly/i10XW6 That's not too bad

Home

I think it was last week when a headline passed by about another Chromium-based browser integrating AI and all that. That was it. Neve saw it again. No one talked about it. No reshared.

Firefox? They got a lot of complaints, feedback, and angered so many.

My take: There are a lot of people who cares about Firefox. While most, if not all, Chromium-based browsers, their users don't care as long as they can browse.

It's like back in the #IE6 era. No one cared as long as their IE6-only website and tools works. Forget about security, privacy, the latest tech.

@fuchsiii @grumpygamer be glad you don't have to support #IE6 anymore...

@dofh_excuses People who still want #IntenetExploder [I call it that way because it's the equivalent of a cyberjihadist when confronted with HTML5 + CSS3] should not be allowed to touch anything more complex than a touchdone landline phone or a lightswitch...

#InternetExplorer #IE6 #Browsers

This is how much I hate Chromium-based browsers, I left my frustration as notes.

```
/* BGN: Dark Age (“spiritual successor of IE6”) engines like Chromium! BOO! */
@supports not (xx: xx) {
…
}
/* END: Dark Age (“spiritual successor of IE6”) engines like Chromium! BOO! */
```

#Chromium is the new #IE6, come back home to #Firefox!

LOL!

Wochenrückblick, Ausgabe 29 (2024-08).

Diesmal mit dem Grund, warum ich mir nach vier Jahren wieder einen zweiten Monitor auf den Schreibtisch gestellt habe, der zweiten defekten Delock 11827 Schaltsteckdose (mit identischem Sympton wie bei der ersten), einem neuen Feature für Bikerouter.de bzw. BRouter-Web, der Verschwörung, die dabei half, dass wir Internet Explorer 6 losgeworden sind, mal wieder Wildschweinen im Garten, etwas Frühling und wie immer Techno.

#Schreibtisch #Monitor #Delock #SmartHome #Tasmota #Bikerouter #BRouterWeb #IE6 #InternetExplorer #Wildschwein #Garten #Frühling #Techno

https://www.marcusjaschen.de/blog/2024/2024-08/

LOL. Found another craziness with #Chromium which #Firefox got right the first time.

`@-supports selector(:lang(\*-latn)` is the only one that works in Chromium. However, none works for wildcard `:lang(\*-C)`.

Firefox accepts `(\*-latn)`, `("*-latn")`, and `("\*-latn")` for both.

Here's a sample code:
```
/**
* NOTES:
*
* @supports selector()
* - :lang(*-latn) = Firefox:no || Chromium:no
* - :lang(\*-latn) = Firefox:yes (insensitive) || Chromium:yes (insensitive)
* - :lang("*-latn") = Firefox:yes (insensitive) || Chromium:no
* - :lang("\*-latn") = Firefox:yes (insensitive) || Chromium:no
*
* :lang(C)
* - :lang(*-latn) = Firefox:no || Chromium:no
* - :lang(\*-latn) = Firefox:yes (insensitive) || Chromium:no
* - :lang("*-latn") = Firefox:yes (insensitive) || Chromium:no
* - :lang("\*-latn") = Firefox:yes (insensitive) || Chromium:no
**/
@supports selector(:lang(\*-latn)) {
:lang(\*-latn) {
color: magenta !important;
}
}
```

1. Firefox and Chromium-based browsers will pass the `@supports selector` check.
2. However, only Firefox will process `:lang(\*-latn)`. To this day, Chromium doesn't support wildcard `:lang(\*-latn)`.

To ensure Chromium-based browsers gets filtered out, use:

```
@supports selector(:lang("\*-latn"))
```

Chromium doesn't know what to do with the wildcard `:lang(\*-C)` selector. It supports one method in `@supports selector()` but not none in `:lang(C)`. The lack of wildcard support in `:lang(C)` selector has been that way for years as well.

#Mozilla Firefox devs really know what they're doing to make the #web better. While Chromium is proving to be the new #IE6, holding us back.

(P.S. I stopped filing bugs to Chromium years ago because they love to shut down people with “no one uses it” and “there's a workaround” so “not fixing”. Why even bother if that's their culture?)

#webdev #CSS