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

Issue 853054 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Cmd-arrow when Omnibox has focus doesn't navigate cursor

Reported by kylel...@gmail.com, Jun 15 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3460.0 Safari/537.36

Steps to reproduce the problem:
With a tab with at least one page in its history:
1. Move focus to the Omnibox
2. Press Cmd-Left Arrow
3. Ensure the Omnibox has focus
4. Ensure the cursor is not in the rightmost position
5. Press Cmd-Right Arrow

What is the expected behavior?
After #2, the cursor should be in the leftmost position.

After #5, the cursor should be in the rightmost position.

After #7, the cursor should move to the respective end of the input area.

What went wrong?
After #2, the page navigates backward in its history.

After #5, the page navigates forward in its history.

This is the expected behavior when the page has focus, but not when the Omnibox has focus. Note that <input> and <textarea> elements in a page still display correct behavior.

Did this work before? Yes 

Chrome version: 69.0.3457.2  Channel: canary
OS Version: OS X 10.13.4
Flash Version:
 
Labels: Needs-Triage-M69 Needs-Bisect
Cc: sindhu.chelamcherla@chromium.org
 Issue 852923  has been merged into this issue.
Cc: susan.boorgula@chromium.org
Labels: -Pri-2 -Needs-Bisect ReleaseBlock-Stable Triaged-ET M-69 RegressedIn-69 hasbisect Target-69 FoundIn-69 Pri-1
Owner: erikc...@chromium.org
Status: Assigned (was: Unconfirmed)
kylelady@ Thanks for the issue.

Able to reproduce this issue on Mac OS 10.13.5 on the latest Canary 69.0.3461.0.
Issue is not applicable to Windows 10 and Ubuntu 14.04.

Bisect Information:
=======================
Good Build: 69.0.3451.0
Bad Build : 69.0.3453.3

Unable to execute the per-revision bisect build as "zero float division error" is coming up. Hence below is the manual changelog URL from Omahaproxy.

https://chromium.googlesource.com/chromium/src/+log/69.0.3451.0..69.0.3453.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1082818

erikchen@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding ReleaseBlock-Stable as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks
Status: Fixed (was: Assigned)
This is fixed on latest canary.

Sign in to add a comment