Consider the option to use drag events instead

[jmbockhorst]

Specifically, using ondragstart instead of onmousedown for the DragStart event. Although users would have to specify the draggable attribute on their elements (which is why it should be optional), it would allow users to handle the onclick event on the draggable element. Currently, handling a click on the drag handler isn’t possible because onmousedown always fires first.

[annaghi]

Thank you for reporting this, I will check how to integrate it.

[K-Adam]

Specifically, using ondragstart instead of onmousedown for the DragStart event. Although users would have to specify the draggable attribute on their elements (which is why it should be optional), it would allow users to handle the onclick event on the draggable element. Currently, handling a click on the drag handler isn’t possible because onmousedown always fires first.

If you would like to handle onClick event on a button inside a draggable item, just use Html.Events.stopPropagationOn "mousedown", like this:

button
  [ onClick MyOnClickMsg
  , Html.Events.stopPropagationOn "mousedown" <| Decode.succeed (Noop, True)
  ]
  [ text "button inside a draggable container" )