-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Problem
Although restarting a stopped workspace when reloading the tab may sound efficient and feel like adding more control because of the limited functionality of the current stopped loading screen, I'm not sure if this is something we want to have in the long run.
Using the browser refresh as a control point to restart workspaces can a) be quite surprising to the user, b) make you feel you are not in control of the application, c) become inefficient for resource management as you can accidentally restart a number of stopped workspaces without need, and more.
For example what happens if you have a group of X stopped workspaces in browser tabs and restore browser tabs after closing the browser or system reboot? This would unnecessarily restart X workspaces, right?
Proposal
Reverting this functionality will probably make sense after making the stopped loading screen more useful in #2192.
/cc @akosyakov because #2085
/cc @csweichel because #2113
/cc @svenefftinge because #2192