RE: AbstractTagImpl.fireEvent() argument order

[Michael Turyn]

Title: RE: AbstractTagImpl.fireEvent() argument order

That seems o.k., except that I'd rather not encourage the JS-oid tendency to leave off arguments, especially as null != <undefined>.

I personally don't mind putting in two null arguments, regardless of where they are; why not keep "fireEvent" for a two-argument method, and something better (I don't feel like suggesting something right now, given that I just remembered that Icame up with "AbstractBlackBoxWidgetBridge") for the full-argument version?