-
Notifications
You must be signed in to change notification settings - Fork 42
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
user feedback when dispVM is opening #137
Comments
NOTE: I'm starting to spec things in Gherkin, and the below is from that spec. Anything named with a capital letter will be referenced in a different Story. The Gherkin Sandbox file may also be cross-referenced for clarity. Scenario: Journalist opens 1 file |
At minimum, I think we'd want to have an "Opening" active state for beta. I don't think we have this in Zep-lin yet, and we do need to decide how it fits in the Files panel & whether the filename stays visible. Adding "blocked on UX" label for now until we resolve. |
Ok, this is on me. I was just about to report this as a bug, but now its back on my radar. Yeah, I'd assumed I'd crashed the disp-VMs from launching, but peeking over to my Qubes laptop, now see it just took for-ev-er. When clicking around multiple sources, it seems like there should be a spot outside the Conversation pane to indicate that files are being worked on getting opened. Brain is going back to the "Briefcase" area of the top bar. Chin is being rubbed. |
Commenting w/ video recorded from Figma to demonstrate. Spinner would be set to auto-cancel after ~30sec or so. However long we feel isn't too long but is long enough, for the toast messages to at least begin; unless the spinner could be set to cancel after the Asset for this lives in the Design System file. Screen.Recording.2021-12-06.at.2.41.00.PM.mov |
we open files in dispVMs, and opening them can take some time - a few seconds.
users can also accidentally grind their workstation to a halt by opening too many DispVMs at once (indeed, I just did this)
we need to:
The text was updated successfully, but these errors were encountered: