Interesting, i do not have this issue nor have I seen it happens before. What groupflow version do you have? Could you get the one from the pallete manager?
Ok using 1.2.15 - I was using 1.2.14 - but still getting the same:
Are you using 5.0.1? 'Cos this doesn't really make sense ...
(btw thanks for removing the labels in the expanded representation 
Are you both using the same OS and Browser?
Mea culpa - sorry for the confusion ...
I am using 5.0.0 but with a bunch of modifications in the editor (for my personal use) and those changes (not quite sure what) is interfering with the movement of the junction nodes.
With a clean setup (both 5.0.0 and 5.0.1), all worked as expected - no movement of the junction nodes along the boundary of the group.
EDIT:
NO - Sorry again, got the bug.
In fact it has nothing to do with my setup (phew!), it's the snap-to-grid functionationality:
When its turned on, everything works well, turn it off and you get the junction node boogie!
So there is probably some event not firing in the case of snap to grid being off ...
Yes, I was looking at your smooth movements and was about to notice you turned off snapping. The snapping was something I added later to the edge junction as unlike my nodes they were freely moving around the verticle borders. I forgot you can ofcourse disable snapping, which my edge junctions dont follow.
I made them now follow the rest of the workspace accordingly. It flows freely with snapping disabled. I also improved the refresh delay when they were snapping so it looks more natural.
Thank you.
It might take some time for the pallete manager to show the update, but npm and github have them.
Yes! Brilliant! Just tested the 1.2.18 in my setup and it works reallllllllyyyyyy nicely!
I love how the undo/redo is supported but the alignment only happens on redraw 
It gave me the idea of creating a stop-motion animation solely based on undo/redo combinations (I am listening to slightly avant garde music ... might have something to do with it)
Sorry just doing some more testing and came up with a couple of other issues, summed up in the gif:
I have two junctions in a group (I often have a junction in a group to "artificial" resize it). Here what is happening is:
- top junction node doesn't quite make it to the edge because it's a member of the group, so I've got a third node to convert the group to a groupflow group
- converting the group causes the second junction node to be dropped out of the group
- the second junction node can't be re-added to the group
- not having a second junction node in the group doesn't allow me to resize the group
- removing the input port for the group and converting the group back to a "normal" group still doesn't allow me to re-add the second junction node
sorry for the edge cases, I just noticed it because I wanted to add a junction node to a "groupflow"-group and couldn't. That's probably not really an edge case rather a bug, the rest of the stuff will probably be fixed if the junction node can be re-added
One tiny other thing: if I hit enter on a junction node, it opens the editor panel:
So your dialog could be replaced by the editor panel if your double-click event did the same as the return button on a junction node. I.e., Currently in NR, the double-click on a junction node does not open the editor panel, only the return key does. This is inconsistent with other nodes (probably a NR bug) since double-click on all other nodes opens the editor panel.
EDIT
CORRECTION: The second junction node remains a member of the group but the group does not resize correctly around the junction nodes:
Certainly not intentional haha. Since the edge junctions were technically not part of the group. Any movement changes that makes the workspace dirty is handled seperately too. So moving a group, first moves the group, then my plugin kicks in and updates the edge junction nodes.
I will see how I can make these into a single action.
Yes, I abused the junctions in this plugin. I stripped them from their meaning thinking nobody really uses them. I wanted users to drag and drop an existing junction onto the groups border. Doing so I made the group not expand in size to allow the junction node to be moved ontop of the edge.
I will handle the junctions into 2 groups.
Internal junction
Junctions that are inside of a group cannot be placed on the edge of a verticle border of that same group. It can never become a edge junction.
External junction
Junctions from outside of the group, can be dragged and dropped on the edge to become a edge junction. You can right click a interal junction and click Remove from group to make it an external junction.
These solutions should fix your other points as well. Since I will handle the junction in general more like a regular junction. I removed any overlaying code that adjusted how it worked.
I noticed this too. Maybe an issue must be raised? 
Or pressing enter to open the editor panel is correct and the rest of the nodes dont work
Very true, the current dialog has been moved to above the description in the edit panel. It feels more native this way.
I have updated github and npm and added a discord channel as I will be away for 2/3 weeks to China. So I will receive pings on my phone through there.
No need for waiting for the pallete manager to update or clone from github.
This should get you the latest groupflow installed on your node red.
> cd .node-red
> npm install node-red-contrib-groupflow
Just tried the 1.3.2 version, great stuff - resizing works now and the junction nodes are included
Also the edit panel for the junction node name now makes the integration much cleaner.
Sandwich tactic: however there is an issue with creating loop connections with junction nodes:
Which can be worked around by connecting a new node. It happens because I clicked on the junction node and not its input port.
The issue might be related how the junction node now handles the mouse up event when the mouse is over it. As shown with the function node: when I drag the wire over the node and let mouse go, the wire disappears. This doesn't happen with the junction node now.
Without the plugin, the junction node does the right thing:
Sorry for being so pedantic and thank you for making this happen
