I am making mouse click events and I’m trying to dispatch it to some node several times in a row. For that I am using the same MouseEvent object and for some reason this approach does not work. Yet, when I create event manually each time, system works. Does anybody know what is the reason for this behavior?
I’ve tried to change the timeStamp, but problem still occurs. I can solve the problem like I mentioned before, but I am interested in how this MouseEvent and corresponding dispatching and handling subsystems really work. MouseEvent specification that I’ve found on MDC pages seems to lack a lot of information.
Tnx for the help!
Update (2023-08-08): It seems that redispatching events is allowed in current browsers. In fact, according to bug 412567, Firefox allowed this since 2008. This was a change introduced to become compliant with the Acid3 test.
Original answer for reference below.
This is actually a security mechanism, dispatching an event that has been dispatched before isn’t allowed. An event always has additional data associated with it, for example whether it comes from a trusted source (user’s keyboard rather than JavaScript code). Some attacks (mostly against MSIE because it had mutable event objects) were using this – they caught a trusted event, changed it and dispatched it again elsewhere (changing might not always be required, dispatching it at a different element is enough for some attacks). In the end disallowing redispatching of events turned out to be the best solution. After all, this functionality isn’t really required: creating a new event object with identical properties (minus hidden data) isn’t exactly hard.
Pretty much all the security issues in this area were related to the file input control. Some time ago Firefox decided to change the file input UI radically and disallow entering the file name directly. I wonder whether this change made redispatching of events a non-issue. I doubt that anybody will be willing to risk opening this can of worms again however.