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

Issue 829719 link

Starred by 2 users
Status: Fixed
Owner:
█ dschuyler@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
sdy@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
ellyjo...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Mouse-Hover is not seen on Omnibox Suggestion List

Reported by aiman.an...@etouch.net, Apr 6 2018 
Chrome Version: 67.0.3390.0 (Official Build) Revision ae47769a6d274cb8eeca0f8e7b9198d0b043975f-refs/heads/master@{#548636}
 	
OS: Win(7,8,8.1,10), and Linux(14.04 LTS).

What steps will reproduce the problem?
1. Launch chrome, open NTP and type something in omnibox.
2. Mouse-Hover on search results and observe.

Actual Result: Mouse-Hover is not seen on Omnibox Suggestion List

Expected Result: Mouse-Hover should be seen on Omnibox Suggestion List

This is a regression issue, broken in M-67  series, and will soon update other info.

Good Build:67.0.3388.0 
Bad Build:67.0.3389.0
Actual Result.mp4
293 KB View Download
Expected Result.mp4
248 KB View Download

Comment 1 by aiman.an...@etouch.net, Apr 6 2018

Labels: RegressedIn-67 Target-67 FoundIn-67
Owner: dschuyler@chromium.org
Status: Assigned (was: Unconfirmed)
Update: 

Unable to provide the bisect using per-revision script, it is giving "RuntimeError: We don't have enough builds to bisect. revlist: []" error and also unable to Narrow down the bisect range as it is giving all Bad Builds, even after increasing the good build range.

Hence providing the suspect via Manual Bisect.

Change-Log URL:
https://chromium.googlesource.com/chromium/src/+log/c8dcacf8e9cf851e26421642548c2cbaf60eb28a..d35f7c6107242ba8ef7df7335ba2eeda07e8da82?pretty=fuller&n=10000

Suspecting: r547929?

dschuyler@ 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.

Note: Issue is not seen for Mac(10.12.6, 10.13.1, 10.13.4) OS.

Thank You!

Comment 2 by rbasuvula@chromium.org, Apr 6 2018

Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Comment 3 by dschuyler@chromium.org, Apr 9 2018

Status: Started (was: Assigned)

Comment 4 by dschuyler@chromium.org, Apr 16 2018

Status: Fixed (was: Started)
This was fixed by ccrev.com/c/1002549 (but I pasted the wrong bug number in the CL).
Project Member

Comment 5 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Apr 16 2018

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.

Comment 6 by dschuyler@chromium.org, Apr 16 2018 

! and by ccrev.com/c/1002549 I meant crrev.com/c/1002549.

That merged April 9th, well before the branch. So a merge should not be necessary.

Comment 7 by gov...@chromium.org, Apr 16 2018

Labels: -Merge-TBD
Removing "Merge-TBD" label per comment #6. Thank you.

Comment 8 by sdy@chromium.org, Apr 18 2018

Cc: ellyjo...@chromium.org sdy@chromium.org
 Issue 830023  has been merged into this issue.
►

Sign in to add a comment