New issue
Advanced search Search tips

Issue 711429 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Using the "transition" CSS property on input[type="text"] prevent it from being focusable via JavaScript

Project Member Reported by chaowentan@google.com, Apr 13 2017

Issue description

Chrome Version       : 57.0.2987.133 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1) Create a simple HTML file with an input[type="text"] element.
(2) Apply the following CSS style:
    input[type="text"] { transition: all 0.1s ease-in; }
(3) Use JavaScript to focus on that <input> element (i.e. element.focus()).

What is the expected result?

The <input> element should be focused.

What happens instead?

The <input> element is not focused. And removing the "transition" CSS property would fix it.

Please provide any additional information below. Attach a screenshot if
possible.

 
Labels: Needs-Triage-M57
Cc: mmanchala@chromium.org
Labels: Needs-Feedback
Could you please provide any sample test case file to check this issue from Chrome-TE end.
It turned out the minimal reproducible example is not as simple as the following (in which the bug cannot be reproduced). I can still reproduce the bug in our app, but unfortunately, it has much more complex CSS style and JavaScript logic. So I won't be able to find the minimal reproducible example any time soon. Please feel free to close this bug if no one else has run into it. 

https://jsfiddle.net/nwp090h9/
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 18 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mmanchala@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Unable to reproduce the issue on Windows-7, Mac-10.12.4 and Ubuntu-14.04 using Chrome stable version  57.0.2987.133 with the provided Url "https://jsfiddle.net/nwp090h9/"
As per comment#3 closing the issue as Wontfix.
 

Thanks.

Sign in to add a comment