So the thing was that at the hackathon I discovered that IE9 doesn't pick up fireEvent from the Element.prototype. We have tried to find a fix but it took quite a while (the fact that my IE9 preview 4 crashed when I opened the dev console didn't help either). I have since posted the bug to the IE9 feedback tracker and Microsoft has since recognized it as bug.
In 1.3 and 1.2.5 we are going the way of putting fireEvent on the HTMLElement prototype, which seems to work in IE9. Before we were able to figure out this fix we decided to rename fireEvent to not collide with the native fireEvent method of IE any more. Given that in 2.0 we will likely move to element wrappers, this problem will go away. This is why, after the fix, we decided to revert the change again so we don't change the API just for the fun of it. I can assure you I was annoyed by the revert too because it took me a while to update all my scripts - but in the end, it is better to keep fireEvent. About our private mailing list: ++ to everything Aaron said. Also, we manage our resources (server, website, etc.) in there. We have huge discussions that aren't necessarily meant for the public - they are between the developers and there is no benefit for anyone in opening it up. We usually invite lots of people if they show a willingness to improve MooTools. Anyone who shows a positive attitude can get on the list. People who do not care enough also do not need to have access. This has nothing to do with us being secretive or anything, we are as open as possible. If you start contributing, we will eventually invite you. Until then, feel free to hang out with use here or in #mootools on freenode On Sep 16, 10:49 pm, Rolf -nl <[email protected]> wrote: > fireEvent is now back I see at github. Is there some discussion where > we can follow things like this? I already updated some beta code, and > it's simple to replace again, though I was wondering how I could be up- > to-date with updates like that (I now stumbled upon this by accident > visiting github for 2 mins)..? > > In the last comment here (by cpojer) I think there will be > triggerEvent in 1.3, but not after 1.3 ("we're not going to > overwrite...")...?https://mootools.lighthouseapp.com/projects/2706/tickets/705-no-way-t...
