[MGNLUI-2756] Moving multiple pages via d&d just moves the first one Created: 18/Mar/14 Updated: 05/Dec/14 Resolved: 07/Aug/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pages app |
| Affects Version/s: | 5.2.2, 5.2.3 |
| Fix Version/s: | 5.3.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Rainer Blumenthal | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
reproducible in Firefox 27.0.1, IE 9, Chrome 33.0.x m (Windows 7) |
||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
1) Select two pages in pages app (i.e. in the same folder). The Move button in the action bar works fine. |
| Comments |
| Comment by Magnolia International [ 06/Aug/14 ] |
|
When I have this tree structure: * foo * bar * baz * qux * fred * waldo If I checkbox-select /foo/baz and foo/qux, then drag /foo/bar into /fred, I end up with completely unexpected results: * foo * bar * fred * baz * qux * waldo (i.e the moved nodes are only the checkbox-ed ones, and the one I dragged did not move)
|
| Comment by Andreas Weder [ 07/Aug/14 ] |
|
What you mention is a classic topic - I remember reading about it in several books (but one in particular: designing web interfaces) in sections dealing with selection and drag and drop. The recommendation is to always include the item you start the drag on to the list of already selected items. In the case you describe, "bar" first get ticked (it's important to show this visually), then the move starts and drags all three items along. The recommendation also includes to always tick an item, when you start dragging it, and to keep it selected once you drop it. That way, it's visually clear what item was worked on and where it ended up. As a matter of fact, the latter *might be a problem in our case, as we don't open a node I drag an item into (which means that the dragged and selected item is actually invisible), but that's another thing we have to fix: all selected items should always be visible - if I close a node with a selected item, the selected item should be deselected (see |