Okay, it looks like a new shortcut has been added? cmd+w, to undo a service group drag? I am also using this shortcut to close a tab, maybe that came to play to break my group somehow

cc @jr - service group feedback

just to add to it, isn't cmd+w the default browser shortcut to close a tab? That's basically disabling the browser behavior in this case. I have to refresh the page cmd+r and while it refresh, press cmd+w so I can close my tab. Otherwise the shortcut is intercepted and nothing happen

Is there any updates that happened today or yesterday around service group?
Yes there were some service group updates recently. I've checked out your project and everything looks normal? Or are you still experiencing a problem.

Is it still localStorage only or there is a plan to save the service groups settings more permanently?
Groups are not saved in local storage. Everyone who has access to the project sees the same groups

so somehow, some of my groups disappeared and I had to re-create them
Hmm not great. If you can reproduce, please let me know! We are working actively on groups atm so will be squashing bugs for the next few weeks

Okay, it looks like a new shortcut has been added? cmd+w
We do have a new shortcut for undo/redo, but it is cmd+z. Does cmd+w really undo and not close the browser tab? That is not at all intended

Hmm not great. If you can reproduce, please let me know! We are working actively on groups atm so will be squashing bugs for the next few weeks
I will let you know if it happen again and leave it in the broken state. Because I recreated my groups straight away yesterday

We do have a new shortcut for undo/redo, but it is cmd+z. Does cmd+w really undo and not close the browser tab? That is not at all intended
Yep, can confirm, cmd+z doesn't do anything for me, but cmd+w does. If I drag a service in my service group, then press cmd+w it undo my drag. I have a french keyboard in AZERTY, which might be the main reason for the issue here. In QWERTY the Z is at the AZERTY's W location

ahhh it is likely the non-qwerty layout causing issues. Hmm not great and a bit strange that the browser API is reporting incorrect values for keyboard event handling. I will squash!

Thanks for fixing it!