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

Issue 756314 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unnecessary focus is seen when clicked on 3 dot menu of chrome://settings/content

Project Member Reported by keerthan...@techmahindra.com, Aug 17 2017

Issue description

Chrome Version:62.0.3188.0
OS:Ubuntu 14.04, Windows

What steps will reproduce the problem?
(1)Launch chrome and navigate to chrome://settings/content
(2)Add something in cookies and click on 3 dot menu

Expected:No focus should be seen on Allow when 3 dot menu is clicked 
Actual:Instead, focus is seen

NOTE:1. When tabbed and entered using keyboard no focus is seen on Allow
     2.Issue is seen in all the 3 dot menus in all chrome://pages
     3.If it's intended, focus shopuld be seen on allow while tabbing using keyboard also 

This is a Regression issue broken in M-62

Manual Bisect Info:
===================
Good Build:62.0.3186.0
Bad Build: 62.0.3187.0
 
Focus_Actual.ogv
1.1 MB View Download
Labels: -Needs-Bisect hasbisect-per-revision
Owner: dtapu...@chromium.org
Status: Assigned (was: Unconfirmed)
Bisect Information:
-------------------
You are probably looking for a change made after 494615 (known good), but no later than 494616 (first known bad).

CHANGELOG URL:
--------------
https://chromium.googlesource.com/chromium/src/+log/a7482a88d73040a616ef53294eeef75ca8b6c5a2..2e27e8ef7352fa68de51b0c59257604c66b9781d

@dtapuska: 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!

Description: Show this description

Comment 3 by ajha@chromium.org, Aug 17 2017

Labels: OS-Mac
Issue is seen on mac canary version: 62.0.3188.0 as well.
Status: WontFix (was: Assigned)
Keyboard events don't generate a hover state.

The bug fix was actually intended to do just the behavior we are seeing in this page that the thing that the mouse is hovering is actually active.

If you try Chrome 61 you will discover it actually highlights after the first mouse move.
Just to know,

In M61, only after first mouse movement focus/highlight is seen but on latest without doing anything[Without moving mouse]focus is seen. Does Comment#4 means this is intended?
Yes is intended. The mouse is hovering under the node, but the webpage wasn't correctly told about it until the first move in previous versions. In 62 that has been corrected and it is told immediately.
Components: Blink>HTML>Focus
Components: -Blink>Focus

Sign in to add a comment