You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found this issue on v1.6.0, and verified that the master branch also has the faulty code.
I searched through the issues for something similar, possibly the problem was introduced by #305.
It seems that there is a bug in handleEvent: evt.preventDefault() is called for the event selectstart, which prevents interaction with contenteditable objects (at least on Chrome 63; Firefox 57 and IE11 are OK --though I do find Chrome's behavior more appropriate). Once I comment out evt.preventDefault() everything is fine.
Note that I had to use the delay option (and therefore as well the forceFallback option, see #659) in order for events to reach the contenteditable object contained in the Sortable target (using a handle might be another way, I haven't tried).
The text was updated successfully, but these errors were encountered:
Found this issue on v1.6.0, and verified that the
master
branch also has the faulty code.I searched through the issues for something similar, possibly the problem was introduced by #305.
jsbin sample here.
It seems that there is a bug in
handleEvent
:evt.preventDefault()
is called for the eventselectstart
, which prevents interaction withcontenteditable
objects (at least on Chrome 63; Firefox 57 and IE11 are OK --though I do find Chrome's behavior more appropriate). Once I comment outevt.preventDefault()
everything is fine.Note that I had to use the
delay
option (and therefore as well theforceFallback
option, see #659) in order for events to reach thecontenteditable
object contained in the Sortable target (using a handle might be another way, I haven't tried).The text was updated successfully, but these errors were encountered: