this continued on until so many major security flaws were found in ie that it drove people who didnt even know what a web browser was to firefox.
this continued on until so many major security flaws were found in ie that it drove people who didnt even know what a web browser was to firefox.
Microsoft had been making developers happy for a decade by giving that exact sort of functionality in local file Explorer, in Word, in Excel, on the desktop, via COM/OLE/VBScript and god knows what else. So they tried it.
The blood/brain barrier between OS and Browser remains up for debate a decade later.
The W3C remains woefully understaffed and even today hasn't solved basic problems that were solved in the dumb terminal era of the 1970s.
There's a lot of shit that got shoved into the browser when we were excited about browsers that shouldn't be there. Likewise there's a LOT of OS-level functionality missing from the browser that may or may not belong there, but which I don't see appearing in the next 10 years either.
It should be noted that the technology behind ActiveX actually started as a Netscape plugin developed by a 3rd party. I remember trying it out way before ActiveX became a thing in IE. It was a crazy idea but back then everything was a crazy idea. There were hundreds of different plugins for all the browsers. Nobody knew what was going to stick. ActiveX stuck because it was Microsoft and because COM was a well established technology.