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

Issue 723560 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Bug



Sign in to add a comment

Non-Regression:Unable to reach the 'Never translate' options through keyboard

Project Member Reported by keerthan...@techmahindra.com, May 17 2017 
Chrome Version:59.0.3071.61
OS: Ubuntu 14.04, Windows

What steps will reproduce the problem?
(1)Launch chrome and navigate to
http://www.stc.com.sa/wps/wcm/connect/arabic/business/largeAndEnterpriseBusiness/largeAndEnterpriseBusiness
(2)In Translate bubble keep tabbing until focus reaches Nope button . Now hit enter and observe

Actual:Unable to open dropdown using keyboard(Focus reaches Nope button but it doesn't go to dropdown. Hence, we are unable to see 'Never translate' options )
Expected:Even with keyboard, we should able to reach the 'Never translate' options 


This is a Non-regression seen from M-32
translate.ogv
1.2 MB View Download

Comment 1 by kavvaru@chromium.org, May 17 2017

Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7 using chrome version 59.0.3071.61.

Comment 2 by yyushkina@chromium.org, Aug 17 2017

Components: -UI>Browser>Translate UI>Browser>Language>Translate
Owner: napper@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by napper@chromium.org, Oct 18 2017

Status: Started (was: Assigned)

Comment 4 by napper@chromium.org, Feb 5 2018

Owner: ----

Comment 5 by yyushkina@chromium.org, Mar 7 2018

Labels: -M-60 M-66 Needs-TestConfirmation
Status: Unconfirmed (was: Started)
Can someone from Test check if this is still an issue in M66?

Comment 6 by kebalaji@chromium.org, Mar 7 2018

Status: WontFix (was: Unconfirmed)
Unable to reproduce the issue on latest M66- 66.0.3359.12 dev on Ubuntu 14.04 and Win 10. And issue is not applicable to latest UI, closing it as wontfix.

Thanks!
►

Sign in to add a comment