Then /window should trigger on open, /dialog -m and -x should trigger ON DIALOG, and I'm sure there are plenty more examples. Changing only /close would be inconsistent, and changing everything would probably break many scripts
It should also be noted that -x in /dialog explicitly states "without triggering any events", which is the standard behaviour.
Also, there is really no gain... Instead of calling /close and putting your script code in the on close event, you would make an alias to close the window and perform the on close events, which would also be called from the on close event if needed. This is how it's done now and it works quite well. If it ain't broke, why fix it?
Finally, there is still the issue of what would happen if you wanted to /close without triggering events (like /dialog -x's current behaviour)? There would be no way to express that.. and there are good reasons to want to.
Given that the benefits aren't very apparent, I personally don't see the need to break scripts that may not be compatible with this behaviour for functionality that is already available via different means.
