1) The testcase uses incorrect syntax (should use event="onmouseover()"). 2) The patch for bug 174404 never worked in builds without XPC_IDISPATCH_SUPPORT defined, as far as I can tell. Not sure whether this was the intent.... Adam? 3) Bug 191579 made for="window" event="onload()" scripts execute inline. This was purposeful. 4) This is totally the wrong component. The parser already handles these correctly; any further work has to be in the guts of the event system.
bug 174404 was about the parser changes needed. Those were made and are still in place. Remaining work to make this "work" has nothing to do with parser....
We never intended to support this script/event syntax in Mozilla in general, the exception was to support it when working with ActiveX plugins due to the fact that most of the content out there used this syntax when dealing with ActiveX plugins. In the non-plugin case this syntax is not very common, and there are perfectly well working standards compliant alternatives. For now, there are no known plans to implement this IE'ism in Mozilla.
Fair enough. I'm working with a web application that uses this and other IE "extensions", and I'm trying in my copious spare time to flush out all the mozilla-incompatible stuff. I was hoping that this was supported as it would relieve some tedium. Please mark this bug as invalid or wontfix, whichever is appropriate. I will add a comment to Bug 174404 clarifying its intent. Adam, could you please change the wording on your ActiveX Plug-in page http://www.iol.ie/~locka/mozilla/plugin.htm regarding "scripting the plugin - For COM Connect - events" as follows: "Mozilla builds with ActiveX support enabled understand the <script for="" event=""> notation for handling events and the plug-in will call these methods in response to events fired by the control." Thanks all.
(In reply to comment #4) > For now, there are no known plans to implement this IE'ism in Mozilla. Let's resolve this bug as WONTFIX then.