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

Issue 706315 link

Starred by 0 users
Status: WontFix
Owner:
pkasting@chromium.org
Closed: Mar 2017
Cc:
nyerramilli@chromium.org
msw@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: In Find in page box unwanted focus stays on 'Previous' button even after clicking 'Next' button.

Reported by ngu...@etouch.net, Mar 29 2017 
Chrome Version: 58.0.3029.41 (Official Build) 3d67f52b399689c5087b12bf6014dfb18fc11e42-refs/branch-heads/3029@{#465} (32/64-bit) 
OS: Windows (7,8,10), Mac (10.11.6, 10.12.1), Linux (Ubuntu 14.04 LTS)

What steps will reproduce the problem?
1) Launch chrome, open NTP and press Ctrl+F (to open find in page).
2) Enter 'a' in input box and press Tab key (focus is on 'Previous' button).
3) Click on 'Next' button and observe 'Previous' button.

Unwanted focus remains on 'Previous' button even after clicking 'Next' button.

Focus should not remain on 'Previous' button on clicking 'Next' button.

This is a Regression issue broken in M-53, will soon update other info
Manual bisect:
Good build: 53.0.2774.0
Bad build: 53.0.2775.0
find_actual.mp4
424 KB View Download
find_expected.mp4
360 KB View Download

Comment 1 by rbasuvula@chromium.org, Mar 29 2017

Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: msw@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:53.0.2774.0 (Revision:400850).
Bad build:53.0.2775.0 (Revision:401299).

You are probably looking for a change made after 401078 (known good), but no later than 401079 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/dc1b7769eed1d73893db064c67e8187a2dfb9b7a..098645c6ee78757f03819207645ff151b8edf01d

From the CL above, assigning the issue to the concern owner

@msw: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url:  https://codereview.chromium.org/2078953003
Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.3 and Able to reproduce in latest Canary #59.0.3054.0

Comment 2 by msw@chromium.org, Mar 29 2017

Cc: msw@chromium.org
Owner: pkasting@chromium.org
I believe this was the behavior we intended. Peter, WDYT?

Comment 3 by pkasting@chromium.org, Mar 29 2017

Status: WontFix (was: Assigned)
Yeah, this is an intentional behavior change.
►

Sign in to add a comment