-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce start with options on the workspaces list #15756
Comments
I believe that if a user ever starts or restarts, regardless of where they comes from, they should see a consistent and reliable interface. It should serve as:
I don't believe we need additional options in menus like "Open with options" or "Open ...". There should just be "Open" and this unified experience. |
This sounds like a good MVC forward and provides more robust user control and freedom. It's also aligned with our product design principles[1]: Less choices, more control[1][2][3]. This is probably also easier to implement now that #15914 (Cc @selfcontained) has landed, see relevant comment in #6874 (comment):
☝️ This means, we could replace all workspace start URLs with prefixing with One small downside in terms of usability with this approach could be that this will always require at least two clicks instead of one for users to open a workspace, but sounds like the trade-off could be worth it. Alternatively, we could skip the step to select options when directly selecting a workspace from the workspaces list using the row or workspace ID, and keep the prompt in all other cases like:
I'll close this in favor of #15979 (Cc @svenefftinge) as it already mentions the ability for the exception:
Thanks for the feedback, @mbrevoort! 🏀 |
Problem to solve
Following up from #15668, opening existing workspaces with a different editor is still a friction as it remains a user preference you have to change every time.
Cc @svenefftinge because #15567
Cc @loujaybee because #13580
Proposal
From the relevant discussions[1][2] (internal):
The text was updated successfully, but these errors were encountered: