WireJack should stop propagation of mouseDown event

[dimerman]

WireJack should stop propagation of mouseDown event

[joshtynjala]

I think I've worked around this by manually stopping propagation in an external event listener, but you're right, it should happen automatically.

[dimerman]

cool.
when can we expect a fix?

awesome lib, BTW

cheers

[dimerman]

oops.. closed by mistake.

[joshtynjala]

I may commit the change in the near future, but I may not release a new SWC right away.

[dimerman]

fair enough. thanks!

[joshtynjala]

Actually, looking this over now, I'm not sure this is something I want to change. There are a variety of events where one could initiate the drag of a parent component, and if I were to stop propagation on all of them, I could affect other behavior in an unintended way. Off the top of my head, mouseDown, mouseMove, and whatever the DragManager uses are three places where a drag outside of the WireJack might be started. It could easily become a mess of targets, priorities and event phases, along with multiple calls to stop the propagation.

[dimerman]

I'm afraid I don't see a scenario where a mouseDown should be handled both by the WireJack and its parent.
If I wanted a container holding a WireJack to get a mouseDown even when clicked on the jack, I would set mouseChildren=false.
IMHO, if the jack is visible and responds to clicks, it should be the sole handler of these clicks...
could you describe a scenario where this does not apply?

could you