search

tigerting98 / pe

0 stars 0 forks source link

Cannot use tab to scroll through autocomplete options #4

Open tigerting98 opened 3 years ago

tigerting98 commented 3 years ago

By having to use arrow keys or the mouse cursor to navigate through autocomplete options slows down the work of someone who types very fast and would like to perform every command without having to move the position of their hands too much. Thus, I feel that a feature allowing users to scroll through autocomplete options and using enter to confirm would be more streamlined for your target audience (fast typists)

nus-pe-bot commented 3 years ago

Team's Response

Lowering to veryLow severity as tester is trying to suggest an alternative to using keyboard when one has been provided (up and down keys). Using mouse cursor is an added benefit.

Furthermore, enter button is typically right above/to the right of arrow keys on most keyboards so is it unclear "without having to move the position of their hands too much." Thus, this bug report is rejected.

This report appears to be an attempt at gaming the PE.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Using the tab key to scroll through the list of available autocomplete actions would allow the user to keep their hands confined to main island of the keyboard where the letters, numbers, spacebar, enter etc. are on most keyboards during usage, avoiding unnecessary movements in the right hand to use the arrow keys or the mouse. In the case of this project, where the target audience are supposed to be fast typists who will mainly expect to type into the CLI, having mouse support is an extraneous feature that does not bring much benefit to the target audience and is not relevant to this issue that I am raising.

While tabbing navigation is generally used for GUI elements, in the case of this application, where the main interaction between the user and the application is through the CLI, the Tab key can be used as a way to allow users to select the desired option from a list of options and would greatly speed up the usage of the CLI. Thus I feel adding a use for the Tab key is reasonable as the application was designed for fast typists who likely want to keep their hands on the keyboard most if not all of the time as using the mouse would just slow them down.

As for the second sentence by the developers regarding the position of the arrow keys, I must argue that on most if not all external keyboards (non-laptop keyboards), the enter key is on the left of the arrow keys and not the right. Using your right hand to press the arrow keys would mean taking your hand off the home row of the keyboard and slow down subsequent typing.

Lastly, the statement that this report is an attempt to game the PE system is uncalled for and seems rather unprofessional.

Thus, I believe that the issue I have raised (not being able to use the Tab key to select the autocomplete option I want) is relevant to the application and should not be outright rejected, as the application is designed for fast typists first and foremost.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: I believe that the use of the TAB key to scroll through autocomplete options would greatly enhance the somewhat clunky usage of the feature, where I would have to move my right hand to the mouse and double click on the option I want or move my right hand to the arrow keys instead of keeping it on the main island of the keyboard, instead of just selecting with TAB and entering to confirm. Perhaps a severity of Low would be fine, but VeryLow downplays the issue too much in my opinion.