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

Issue 686605 link

Starred by 10 users
Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Please enable *Right* Alt + Arrow too

Reported by weitzhan...@gmail.com, Jan 30 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
You recently removed the backspace button which I'm not too happy about it, because I don't like pressing two buttons in place of one, especially for such a trivial task as navigating backward/forward.
Anyway, not only you require the user to use two buttons, but you require them to use two hands, because only left alt works. The right Alt doesn't do anything. And since there is a huge gap between the left Alt and the arrows, you have to use two hands in order to navigate backward/forward.
This is outrageous, especially when coming officially from Google that is supposed to make the web more responsive.

What is the expected behavior?
Note: Although I don't thing is related, I'm using the US International keyboard.

What went wrong?
Please enable both ALT keys when pressing Alt+Arrow for navigation.

Did this work before? Yes 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

Comment 1 by woxxom@gmail.com, Jan 30 2017 

US (default) keyboard layout: successful navigation on AltGr + arrows.
US (International) layout:    Chrome ignores AltGr + arrows. 

Apparently the bug happens because AltGr is used to input accented characters. On the other hand, the arrow keys aren't used to type anything [1] so Chrome should handle them just like it does in US-default layout.

I see the issue in randomly tested Chrome versions 31, 45, 55, 58. It seems the bug was there since the very beginning. Could be even a Windows thing that needs a special workaround.

  [1]: https://en.wikipedia.org/wiki/AltGr_key

Comment 2 by weitzhan...@gmail.com, Jan 30 2017 

Let me just add that I also have Hebrew keyboard installed on my machine, and Chrome also ignores the AltGr key on the Hebrew keyboard.

This is issue is a bummer. It makes no sense to use two hands to go backwards.

Comment 3 by nyerramilli@chromium.org, Feb 1 2017

Labels: Needs-Milestone

Comment 4 by dr.lo...@gmail.com, Feb 2 2017 

Same on a French layout.

Comment 5 by weitzhan...@gmail.com, Feb 5 2017 

Just updated to Chrome 56 and I can confirm the issue hasn't been targeted yet.
This bug is unbearable.

Comment 6 by msrchandra@chromium.org, Feb 6 2017

Cc: msrchandra@chromium.org
Labels: -Needs-Milestone M-56 Needs-Feedback
Tested the issue on Windows 10 on Latest Stable# 56.0.2924.87 and could successfully navigate using ALt + Right or Left Arrow.

@weitzhandler -- Could you please upgrade your Chrome to latest stable and provide us the recent behavior which would help us triage further.
Thanks in Advance.

Comment 7 by woxxom@gmail.com, Feb 6 2017 

#6, please pay attention to the bug description and comments above and use a US international keyboard layout and AltGr key to the right side of the space bar.
Project Member

Comment 8 by sheriffbot@chromium.org, Feb 12 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by weitzhan...@gmail.com, Feb 12 2018 

@ sheriffbot@chromium.org
This is definitely still an issue.
Try using *US-International Keyboard* layout on Windows, and press Alt Gr + Left arrow, in order to navigate backwards. Nothing happens. It's so frustrating that Google's solution to navigate back is forcing you to use both hands! 
Shame on Google for having this issue archived after it being open for so long neglecting all users' repetitive comments.

Comment 10 by thibaut....@illogika.com, Feb 12 2018 

yep

Comment 12 by weitzhan...@gmail.com, Feb 12 2018 

Please star the new issue I opened.
►

Sign in to add a comment