d3/d3-drag

Issues

• Listeners may not see the latest data.

  #14 opened 4 years ago by mbostock
  1

• preventDefault on mousedown and touchstart by default?

  #9 opened 9 years ago by mbostock
  6

• Allow dragging on elements with no data by default.

  #18 opened 9 years ago by mbostock
  0

• Stop propagation on consumed events.

  #16 opened 9 years ago by mbostock
  0

• Rename drag.subject to drag.data?

  #17 opened 9 years ago by mbostock
  2

• Ignore “ghost” mousedown after touchend.

  #15 opened 9 years ago by mbostock
  2

• Examples.

  #8 opened 9 years ago by mbostock
  8

• Force examples shouldn’t set target alpha to zero on end.

  #13 opened 9 years ago by mbostock
  0

• Documentation.

  #11 opened 9 years ago by mbostock
  1

• drag.filter is awkward.

  #12 opened 9 years ago by mbostock
  0

• Set -moz-user-select: none since Firefox doesn’t yet support selectstart events.

  #1 opened 9 years ago by mbostock
  0

• Cache getScreenCTM on start?

  #5 opened 9 years ago by mbostock
  1

• afterdrag event?

  #7 opened 9 years ago by mbostock
  2

• click.stopPropagation?

  #10 opened 9 years ago by mbostock
  0

• Ignore multiple simultaneous drags on the same element?

  #3 opened 9 years ago by mbostock
  3

• Implement dragstart, selectstart, click suppression as listeners.

  #6 opened 9 years ago by mbostock
  0

• How to expose state to callbacks?

  #4 opened 9 years ago by mbostock
  1

• Make the drag behavior independent of the target element’s data?

  #2 opened 9 years ago by mbostock
  1