#ie6 — Public Fediverse posts

#ABB erweitert sein Portfolio hocheffizienter #Antriebssysteme und bietet magnetfreie #IE6 #SynRM Motoren für ein breites industrielles Anwendungsspektrum an.

Die #Motoren senken den #Energieverbrauch deutlich und ermöglichen spürbare CO2 Einsparungen über die Lebensdauer. Sie sind zu 98 Prozent recycelbar und lassen sich in bestehende Anlagen wie #Pumpen oder #Ventilatoren integrieren.

https://www.lebensmittelverarbeitung-online.de/produktion/ie6-motoren-erhoehen-energieeffizienz-industrieller-antriebe-deutlich

#Industrie #Energieeffizienz #environment #energy #Elektrifizierung

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

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

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.

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!

@cory
This is history!
#Web #IE6

"It’s Easier To Ask Forgiveness Than To Get Permission" Grace Hopper

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

@dams don’t use table for content. This element is only useful to design your webpage 🥁 #ie6

Tiens, ça fait longtemps que je n'ai pas vu cet écran de #IE6 en public ! C'est presque du #retrocomputing à ce stade.

I remember a time when #browsers only supported having a single page open at a time. It wasn't that long ago; I could be wrong (please correct me if I am), but I think #Chrome was the first to offer tabbed browsing, and then the others following suit.

Was #IE7 the first version of #InternetExplorer to support it, or was it supported from #IE6 already?

I started my working life when #IE3 was still the standard, and I remember being astounded along with everyone else at the advent of #IE4 and the Active Desktop. Remember the Active Desktop? You could carve out pieces of websites and put them on your desktop and have them refresh automatically. People used it for news feeds (social media wasn't a thing yet) or weather reports or even just to show the time.

*sigh* These are just more things that the #GenZ generation will never understand. Along with the fact that not all #GIFs are animated (in fact, in the old days, very few of them were because adding extra frames took up unnecessary disk space and bandwidth).

#computers #Internet #history #nostalgia

@metlstorm

Can we have a content warning before there is a mention of IE6 again on the 'cast? 😉

#ContentWarning #IE6

We should give #Microsoft some credit for things like inventing AJAX (XMLHttpRequest), #TypeScript and #ReactiveX. Also, developing #VsCode, #Halo and #AgeOfEmpires. And some decent hardware, like keybords and mice. They're not only #WindowsMe and #IE6

Listening to a really old episode of the #StackOverflow podcast. They're discussing #IE6. Scream😱 . Still have nightmares about all the HTML/CSS workarounds my colleagues had to put in place just for it. And how many years were #NHS #Scotland folk using it way after they were supposed to. Canny abide client-side stuff. Write once all day long.

@volkris All very good points! But, at the end of the day, if reach is their goal, then limiting themselves to a platform that is, to quote Bridgy, “burning”, is contradictory. In the first place, many of them joined because it became popular. But, now, even with the growing popularity of the fediverse, and other platforms, they don't want to.

Think of it this way. Majority of Facebook and Twitter users joined these platforms because knowing that they will have to start from scratch and convince their family and friends to sign-up. They knew they have to sacrifice their existing #Friendster and #Myspace connections. Yet, they did.

Years later, these same people are refusing to create an account in other platforms (not just the fediverse), and the most frequent reason given is “lack of connections”.

Or, an example from the business side, #IE6 in South Korea. The financial infrastructure there was heavily dependent on features only available in IE6. For years, they refused to leave IE6. They cited most, if not all, of the things you pointed out.

Eventually, Microsoft called it quits and killed IE6 for good. Probably got tired of waiting. IIRC, SoKor had to pass a law to force their banks to move away from IE6 and to guarantee there won't be an ‘apocalypse’ once IE6 is gone for good.

I think a combination of both is happening with many of these companies. They've forgotten how they started, and why they have those accounts. They went through explaining and convincing, they went through trying to get their projects signed-up, trained people, and so on. The difference is, today, they don't want to do it because… for those reasons. Are they going to wait until the other platforms turn into ashes?

I do understand your points, very valid, I've been through that myself, chased their signatures, prepared presentations, but at the end of the day, it all comes down to our target market. That target market split into various platforms. Just like ten or so years ago, we followed where they were flocking. We should be ready for any changes in the landscape. If the other platform turn into ashes, we are already set up and running in other platforms. Otherwise, a lot of projections and targets will go into red.

Then again, if someone is already pushing for these things and kept getting refused no matter what explanation they gave, someone is going to enjoy an #IToldYouSo moment. ^_^;; (LOL. I also experienced that moment once.)

@youronlyone @sharearea

@andy It’s going to be so sad when #AppleBrowserBan goes away as then, like with #IE6, we have to find something else to project our anger at

Mozilla #Firefox doing an existential crisis

#IE6

Also, why the hell does blink/chrom[e|ium] fuck up the scroll-position if the element scrolled to isn't >13px wide?

And why in the name of all flying fucks does scroll-margin-top only match for gecko and scroll-padding-top only for blink in the use-case involving the scroll position fuckup?

And how are issues like this even a thing after #IE6 was deprecated?

@anarchosynthiecat well, it is what it is - if firefox and other browser engines die out, we are going to have the same nasty situation as we had with IE 6.

Like the situation was in 2000: Want to use 100% width in your CSS _or_ table width attributes? No chance in hell - IE 6 doesnt support it yet! #ie6 #browserhell #iedoesntlikeme

Quick reminder: Why you indeed should use Firefox
https://www.dedoimedo.com/computers/firefox-why-you-should-use.html

#darkages #browserwars #ie6 #browserdiversity #monopoly