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

Issue 702133 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
nyerramilli@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 : Unable to type anything inside 'history search box' after dismissing the toolbar.

Reported by yfulgaon...@etouch.net, Mar 16 2017 
Chrome Version : 59.0.3043.0 (Official Build) fe785a58e31217e1ef0e1c8946a4e853829371f8-refs/heads/master@{#457297} 32/64 bit
OS : Windows (7,8,10), Mac (10.11.6, 10.12.1, 10.12), Linux (14.04 LTS)

Precondition : Please make sure that chrome has at least one history record in chrome://history.

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://history and check the checkbox of first history entry.
2. Click on "1 selected" text in toolbar and press 'Ctrl' + 'A' keys to select the text.
3. Click on 'Cancel' (X) icon in toolbar (toolbar gets dismissed) and now click inside "Search history" search box and try to type something, observe.

Actual : Unable to type anything inside 'history search box' after dismissing the toolbar.
Expected : User should be able to type inside 'history search box' after dismissing the toolbar.

This is a regression issue broken in ‘M-58’, below is the Manual Regression range and will soon update other info.
Good build : 58.0.3012.0
Bad build : 58.0.3013.0
Actual_history.mp4
761 KB View Download
Expected_history.mp4
756 KB View Download

Comment 1 by brajkumar@chromium.org, Mar 16 2017

Labels: hasbisect-per-revision
Owner: yosin@chromium.org
Status: Assigned (was: Unconfirmed)
Bisect Information:
---------------------
You are probably looking for a change made after 450369 (known good), but no later than 450370 (first known bad).

CHANGE-LOG URL:
-----------------
https://chromium.googlesource.com/chromium/src/+log/18375370aff250f59f5ef624ecf686d860377ece..d892f9592860691ae9a782c12260c94ed6bd1a63

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

yosin@ Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 2 by krajshree@chromium.org, Mar 23 2017 

Unable to reproduce the issue on Win-10 and Mac 10.12.3 using latest canary #59.0.3048.0.

yfulgaonkar@ - Could you please check the issue in latest canary #59.0.3048.0 and update the thread.

Thanks...!!

Comment 3 by avsha...@etouch.net, Mar 24 2017 

With response to comment #2,

Retested above issue in latest canary #59.0.3050.0 build on Win-10, Mac(10.11.6, 10.12.1) OS and issue is not reproducible. It is working as intended.

Thank you!

Comment 4 by yosin@chromium.org, Mar 25 2017

Owner: ----
Status: Fixed (was: Assigned)
Mark Fixed per #c2 and #c3.

Maybe http://crrev.com/2749513004 fixed this issue.
►

Sign in to add a comment