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

Issue 758066 link

Starred by 4 users
Status: Archived
Owner: ----
Closed: Sep 13
Cc:
█ susanjuniab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Shift+KeyPadEnter in "Find on page mode" doesn't iterate in reverse order

Reported by petr.ko...@bigcommerce.com, Aug 23 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Press Cmd+F and enter a search keywords such as "a"
2. Press Shift+KeyPadEnter (i.e. Enter on a keypad, not the main Enter key)

What is the expected behavior?
It should iterate over "search results" in a reverse order

What went wrong?
It iterates over "search results" in a regular order.

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

Note that Shift+Enter (i.e. the main Enter key) works fine. Only the "KeyPadEnter" doesn't work properly.

Comment 1 by susanjuniab@chromium.org, Aug 23 2017

Cc: susanjuniab@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
petr.kotek@ Thanks for the issue..

Tried this issue on Mac OS 10.12.6 using latest stable 60.0.3112.101 and Canary 62.0.3193.0 with the below steps.

1. Launched Chrome and opened a random web page.
2. Pressed cmd+F and entered a keyword to search.
3. Pressed Shift+Enterkey on the keypad and can observe that the search results is iterating in a reverse order as expected.

Can you please confirm what is the difference between KeyPadEnter and main Enter Key?

Thanks..

Comment 2 by petr.ko...@bigcommerce.com, Aug 23 2017 

Thanks for checking.

I'm using Apple A1243 wired keyboard and it turns out, it sends 0x03 key code for KeyPadEnter and 0x0D key code for regular Enter key.

(see also screenshot taken from "Key Codes" app showing key codes for Enter, KeyPadEnter, Shift+Enter, Shift+KeyPadEnter).

I can also try to replicate it on another macbook with the same keyboard in few hours.
Screen Shot 2017-08-23 at 4.47.30 pm.png
66.2 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 23 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 4 by petr.ko...@bigcommerce.com, Aug 23 2017 

ok, i tried it on another Macbook (Mid 2015) with macOS Sierra (10.12.6) with the same Apple A1243 keyboard and I experience the same issue: KeyPadEnter (in the bottom right of the keyboard) issues 0x3 key code and results in the problem I described in the very first post.

In any other use case KeyPadEnter (confirming URL, "Find in Page", ...), it behaves same as regular Enter key. Only in combination with Shift, it doesn't result in result search as described previously.
a1243_keyboard.jpg
21.1 KB View Download

Comment 5 by susanjuniab@chromium.org, Aug 24 2017

Components: -UI IO>Keyboard
Labels: TE-Hardware-Dependency
petr.kotek@ thanks for the feedback.

As we do not have the required keyboard to test this issue, requesting the appropriate team to look into this and help in further triaging.

Thanks..

Comment 6 by shrike@chromium.org, Sep 15 2017

Components: UI>Browser>FindInPage
Status: Untriaged (was: Unconfirmed)
[mac bug triage] confirmed in 62.0.3202.18.

Comment 7 by sdy@chromium.org, Sep 26 2017

Labels: Hotlist-CocoaBrowser
Status: Available (was: Untriaged)

Comment 8 by robliao@chromium.org, Sep 13

Status: Archived (was: Available)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Comment 9 by robliao@chromium.org, Sep 13 

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment