Multi-select doesn't move point associated with line

[jgscherber]

When select both a line and a node on that line, it'd be nice if a dragging action always moved the selected node, instead of any other nodes at the same location. See gif below for the "bad" behavior. The use case is largely around unhooking areas from roads. I don't want to move the road node just to get at the area node to move it.

(Although looking at the gif again, maybe the "good" behavior is: when a line is select, prioritize multi-selecting nodes on that line when they overlap with other nodes)

[quincylvania]

I think this is the task behind #7984, but I'm going to leave this issue open instead since it seems more focused (and has a nice gif 😄).

[AntMadeira]

In areas with landuse connected to highways (and other elements) it's a nightmare to try and detach them with iD due to this problem. Btw, this doesn't happen only on intersections, but in the entire shared lines between landuse and highways.
I'm just bumping this topic hoping it can get some attention.

Regards.

[1ec5]

This issue is about what happens when part of all of the landuse area is already disconnected from the adjoining highways. If all you need to do is detach the landuse area from highways, select the area and use the Disconnect command. (You may need to zoom to fit the area if it’s too big.)

For more limited disconnections, I use this workaround:

1. Drag the road out of the way.
2. Select the previously obscured node.
3. Undo the move.
4. Use the keyboard shortcut (M in English) to start moving the multiple selection without interference from the road.

[AntMadeira]

I'm aware of that process, but when you have to do this dozens of times in just one changeset it's a nightmare...

What I end doing many times is detach the entire landuse area and reduce it with Shiff + "-", but that's not an ideal solution, since it only works if the landuse is not connected to other elements.
Using Shift+select node+M also works sometimes, but not always.
What should happen is being able to move just the nodes from the selected element.

All this could be avoided if there was a warning when a mapper attaches landuse to highways...