Plus, NaCl is closer than "something like" to ActiveX. What do you consider to be the salient difference between the two technologies?
Wine has been a long time in the making and certainly wasn't ready to be integrated into Mozilla for ActiveX compatibility on Mac OS, Linux, or even alternative browsers on Windows in 1996, so it's kind of a silly point to make.
http://src.chromium.org/viewvc/chrome/trunk/src/ppapi/
Why are you ranting about things you clearly know nothing about?
> The NPAPI port for other browsers was abandoned
You're bitching up and down this thread about standards, and now you're defending the ancient, non-standard Netscape plugin architecture? Do you have any clue what you're talking about, or are you just here to be anti-Google?
Webkit and Mozilla being open source means that no single company can control the projects or add a proprietary single-platform exception to them.
Now, a company could FORK Webkit/geecko and add something like ActiveX to it, but the fork wouldn't be part of webkit/geecko project anymore, and we'd still have webkit/geecko proper. For example, Google added NaCL which is something like ActiveX to Chrome, but not to Webkit itself.
Open source is one thing, but if you're not able to convince Google and Apple to ship your changes, you've hit a wall. FF implementing support for the WebKit extensions is what will break the web back into the IE-dominant era.
Having a competing browser is useless if it won't work with the content that people want to use.
Or, if were webkit not open source then it would probably not end up being a joint apple-google production. Joe-bob's ideas for CSS that he compiles into Firefox himself may not be relevant, but eventually if FF sucks enough some fork of it will displace it as it did for Mozilla (cf. V8 displacing JavascriptCore) per some version of Kuhnian paradigm-shift.