Environment: Win 10. node-red v1.1. node.js 12.16.3. Chrome.
I've been using v1.1 extensively for the weekend - moving VERY large automation projects to it.
I really love the 'group' functionality - this is a game-changer as it encourages 'blocks' (groups) that document our code and make it much more comprehensible. Absolutely AWESOME!
There is something funny going on occasionally with create / copy / move / paste into 'groups'.
Several times it has given a 'slow page - do you want to wait' message. Reloading it (F5) fixed it.
Just now received error: "cannot add nodes with different z properties"
This was after I selected a lot of nodes and then did CTRL-SHIFT-g to group them.
Afterwards, to debug it, I then used CTRL-V into a blank area OUTSIDE where the Group would be created and sure enough - there were quite a few nodes pasted BUT several right on top of each other - in a jumbled-up pile.
I'll try to reproduce and capture the scenario & Chrome console when / if this occurs next.
Please don't take this as a negative: I like v1.1 enough to move 8 developers over to it over the next couple of weeks.
Update - went and looked in Chrome console.
Hmmm... Restarted node-red. clean copy of Chrome.
Opening a complex sub-flow (with multiple sub-flows in it) also with multiple Groups on it . Immediately generates 44 errors in Chrome console. I'm not sure it is significant but am willing to help reproduce / resolve in any way.
It is 'acting' like there is a group applied to some of the nodes - but no boundary / border visible.