3 ms·
The linked article includes an example of the "commented backslash hack," a variation on point #3 in this article Fell out of use because "nobody uses IE for M
by cantSpellSober 3y ago
The linked article includes an example of the "commented backslash hack," a variation on point #3 in this article
Fell out of use because "nobody uses IE for Mac" :)
- dylan604 3y agoIE for Mac was so atrocious, there's a chapter dedicated to it in iWoz.
- chrisfinazzo 3y agoAs I understand it - I was a bit young when it happened, so all I have are secondhand accounts - IE 5 on Mac was substantially better that other browsers due in part to its CSS support.
- dylan604 3y agoThe chapter on IE for Mac in iWoz has nothing to do with how the browser render engine worked. It is about how the OS behaved after it was installed.
- asadotzler 3y agoTasman was way ahead of Trident actually. It had many problems Gecko had in that the web didn't care much for standards so implementing the standards, even well, wasn't considered a selling point. It was years of mostly Mozilla effort to make standards matter enough that web developers came around to them and then Tasman was viewed as an amazing pioneer alongside Gecko.
- Klonoar 3y agoIt amazes me to this day that IE for Mac wasn't even the Trident rendering engine.
- asadotzler 3y agoWhile at Mozilla for a quarter century, I got to work for many years with one of the people who made Tasman, Mac IE's engine. It was a phenomenal engine from what I learned. I wasn't on Macs in that era so didn't use it much, but knowing today what I've learned about it, I believe it to be one of the better pieces of software Microsoft people ever built.