Description
At the very least this is a mismatch between actual behaviour and documented behaviour. The docs say click events are dispatched when the left mouse button is pressed and released on a display object:
EaselJS/src/easeljs/display/DisplayObject.js
Lines 546 to 551 in aea6424
This matches the behaviour of native dom events, where click is fired for the primary mouse button but not the secondary button (unlike mousedown/up which fire for any mouse button).
However EaselJS doesn't listen to native click events on the canvas element, instead it dispatches its click events from the mouseup listener. The only check is that the mouseup occured over the same display object as the originating mousedown:
EaselJS/src/easeljs/display/Stage.js
Line 711 in aea6424
Should EaselJS be checking the mouse button before dispatching the click event? (That's what PixiJS does)
Or are the docs wrong, and click events are supposed to be dispatched for the secondary mouse button?