BurningTreeC
afe14b47b5
draggable widget: actions on drag-start and drag-end ( #3203 )
...
* pass drag-start end drag-end actions to draggable
* Update dragndrop.js
* Update dragndrop.js
* Update dragndrop.js
* Update dragndrop.js
* Update dragndrop.js
* renaming dragstart/dragend -> start/end
* renaming dragstart/dragend -> start/end
* adding docs
2018-04-08 10:29:17 +01:00
BurningTreeC
42660b05a7
check if dataTransfer is undefined ( #3093 )
...
this prevents an error when dragging elements not by mouse where dataTransfer can be undefined
2018-01-20 17:28:10 +00:00
Jermolene
1e106a8f3d
Better handling of dropeffect
2017-03-28 15:09:36 +01:00
Jermolene
f3cab3753e
Don't set draggable property for links
2017-03-28 13:05:00 +01:00
Jermolene
d3fe4f600a
Partially fix drag and drop on IE11
...
These changes allow drag and drop to work with one issue: <a> links are
not draggable; draggable divs, spans, buttons etc. seem to work fine.
There’s some issue with IE11 that I don’t understand.
For testing, you can force links to become spans by changing line 64 of
$:/core/modules/widgets/link.js to:
var domNode = this.document.createElement("span");
2017-03-27 09:59:40 +01:00
Jermolene
1f860bd04e
Fix problem with dragging links
2017-03-23 17:52:15 +00:00
Jermolene
b1ed77d6b8
Switch drag image to use draggable DOM node
...
We’ll still support dragging pills, but dragging the DOM node image
seems to look better in most situations.
2017-03-23 17:02:26 +00:00
Jermolene
8f1114960a
Refactor draggable stuff for easier reuse
...
And in the process, make the button widget draggable.
Unfortunately, Firefox has a bug that prevents buttons from being
dragged (see https://bugzilla.mozilla.org/show_bug.cgi?id=568313 and
https://bugzilla.mozilla.org/show_bug.cgi?id=646823 ). So we have to use
the “tag” attribute to make it use a different element.
2017-03-23 14:23:33 +00:00
