Skip to content
This repository has been archived by the owner on Jan 22, 2021. It is now read-only.

"New Task" priority field sends keyboard events to the previously selected task #297

Open
Bujiraso opened this issue Feb 7, 2014 · 0 comments
Milestone

Comments

@Bujiraso
Copy link

Bujiraso commented Feb 7, 2014

Steps to recreate context: Select a task on a list. Create a new task by clicking the Add button or pressing CTRL+N. Press tab twice or click to select the priority field.
Expected function: Space button changes the priority of the new task. Enter does nothing. All other keys do nothing
Actual function: The expected function occurs from the space bar, but the previously selected task is also checked or unchecked (since the space bar doubles for this purpose outside of task creation). The enter button expands and contracts the previously selected task. If the task is expanded and other keys (e.g. letter keys) are typed, they are forwarded to the previous task, possibly overwriting its prior values and focus on the new task is lost.
Proposed solution: Upon creation of a new task, it appears that the previously selected task remains selected. Having the creation of a new task call to deselect the previous task may be the solution.

Additional Notes: This may be related, so I won't create a new bug for it, but, when in the priority field, the escape key also does not compact the task as I would expect it to. This is more nuisance than problem, but worthy of note.

@stayradiated stayradiated added this to the 1.5 milestone Feb 8, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants