Description
The default behaviour of Dojo DnD is to capture Ctrl and Shift for ‘multiple selection’ and ‘copy’. There seems to be some conflict with our handling of these key events which is causing some unpredictable behaviour.
Environments
Windows XP SP2 Firefox 2.0.0.4
Issue Links
Comments
-
Antranig Basman commented
2007-06-27T09:49:37.000-0400 Serious deficit which causes the component to “fail” - i have managed to persuade it to try to drag multiple items this way, with “hilarious results”…
-
Colin Clark commented
2007-07-30T14:43:20.000-0400 We’ll take the following steps to resolve this one:
1. Short term: disable or swallow use of the shift and ctrl keys for multiple selection, making the hilarious results Antranig saw impossible.
2. Change the Lightbox/Reorderer to use a modifier other than ctrl for moving images with the keyboard (because it conflicts with the familiar mode of multiple selection on most platforms).
3. Add explicit support for multiple selection of items with both the keyboard and mouse. -
Anastasia Cheetham commented
2007-10-03T17:41:40.000-0400 In dojo 0.9 beta, multiple selection can be disabled by setting the Source’s “singular” parameter to true e.g setting “dndlb.singular=true” or passing the parameter in to the Source constructor.
-
Anastasia Cheetham commented
2007-10-04T15:46:05.000-0400 I’ve disable multiple selection (rev 12545) - it shouldn’t be a problem.
I’ve been unable to produce any copy-related errors i.e. errors where dojo’s use of the CTRL key for copying causes problems. Mixing the CTRL key and dragging does cause some style issues that I’m looking into addressing, but if anyone can provide instructions for reproducing any copy-related bugs, that would be very helpful.
-
Anastasia Cheetham commented
2007-10-05T12:56:28.000-0400 I believe the CTRL-key related strangeness is not related to dojo’s copy functionality. That strangeness is now captured in FLUID-44
-
Michelle D'Souza commented
2007-10-22T17:12:41.000-0400 Since we’ve moved to using jQuery UI’s drag and drop this is no longer an issue.