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
keyboard shortcuts in web UI #439
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
Keyboard shortcuts are infuriating unless the UI reacts "instantly" (< 100ms). I think if this were to be done then a lot of the work would be making the pages be as responsive as possible. |
This should be easier to approach once our full Elm single-page-app rework finishes (soon). |
I would also love keyboard shortcuts, but also for triggering events, such as |
@wendorf +1 for the "a" and "t" shortcut |
Currently we have:
cc @Lindsayauchin for designs on help screen overlay |
|
honestly we should just implement vim key bindings.....but not today |
concourse/concourse#439 Signed-off-by: Mark Huang <mhuang@pivotal.io>
concourse/concourse#439 Signed-off-by: Mark Huang <mhuang@pivotal.io>
I would like to see concourse web UI accept keyboard navigation. I dislike using the mouse, and this is doubly-true for the pipeline view, where a small mouse movement while clicking on a job means sometimes my click isn't registered as a click, but as a drag, and hence I do not navigate to the page I expect, but instead remain on the pipeline view, moving the image very slightly.
Other pages could benefit from keyboard shortcuts too, like the builds page (e.g. h/l for next/previous, j/k for scrolling). I'd love some way to 'jump to next failure' but that is probably too hard to solve, and is likely out of scope for keyboard shortcut MVP.
If we implement keyboard shortcuts, I'd also like to see
?
be a global shortcut (i.e. on all pages) for help.The text was updated successfully, but these errors were encountered: