New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769017 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Arrow key behavior when multiple files are selected/focused

Project Member Reported by mcirimele@chromium.org, Sep 26 2017

Issue description

Chrome Version: 63.0.3223.0 9976.0.0 Caroline

What steps will reproduce the problem?
(1) Start with multiple files selected or in focus
(2) Use the arrow keys to go up or down

What is the expected result?
If the user presses up arrow, the file above the top selected/focused file gets focus. If the user presses the down arrow the file below the bottom selected/focused file gets focus.

What happens instead?
A seemingly random file somewhere in the middle gets focus.

 
Cc: weifangsun@chromium.org
Labels: -Pri-3 OS-Chrome Pri-2
Owner: fukino@chromium.org
Status: Assigned (was: Untriaged)
Raising the priority of this one for M63 - fukino@, can you assign to the right eng?
Status: WontFix (was: Assigned)
It actually is not random.
On UP/DOWN key, the previous/next index of the last selected item's index (which is called 'lead index') will be focused.
This behavior is common in file managers in other platforms.

Please reopen this if the expected behavior is not working, or we should change the expected behavior.
Status: Assigned (was: WontFix)
Thanks for the clarification Fukino-san. 

It felt random to me because I didn't understand that the lead index was the chronologically last selected file. I think it be good to change that to the last file in the list instead. This is what MacOS does but I'm not sure about windows. I'm re-opening for that change. 
The Finder.app on macOS(10.12.6) has the same behavior with us (i.e. the lead index is the chronologically last selected file).
Could you double check?
Oh I'm sorry you are totally right. I thought for sure that I tested this thoroughly. I will discuss with weifangsun@ and see how we want to move forward. 

Comment 6 by fukino@chromium.org, Oct 11 2017

Status: WontFix (was: Assigned)
Marking WontFix(WAI) for now.
mcirimele@, feel free to reopen this (or file a new one) if we should change the current behavior. Thanks!

Sign in to add a comment