> My guess is that the details of implementation for both of the mousedown and mousemove events are slightly different between chrome and Firefox, and this ends up in radically different behaviours because of the "on the fly" instantiation of the event listener.
After checking it out further, it could also be that somewhere the math for positioning is slightly off. On chrome, whenever I click the panel, it shifts a couple pixels down. This might be the trace that the math doesn't add up here and that our code is creating a move event without any actual movement.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
