input autocomplete setting is not respected when coming from a second input field
Reported by
mfa...@usinternet.com,
Apr 27 2016
|
||||||
Issue description
Chrome Version : 49.0.2623.105
URLs (if applicable) :
Other browsers tested:
Safari: OK
Firefox:
IE:
What steps will reproduce the problem?
(1) Have a form with three input fields such as the following:
<!DOCTYPE html>
<html>
<head>
<title>Bug Demo</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<div>
<p>Enter something here, no autocomplete.</p>
<input type="text" autocomplete="off" autocorrect="off">
</div>
<div>
<p>Click on this input then go back to the first and autocomplete is enabled.</p>
<input type="text" autocorrect="off">
</div>
<div>
<p>Click on this input then go back to the first and autocomplete is disabled again.</p>
<input type="text" autocomplete="off" autocorrect="off">
</div>
</body>
</html>
(2) Go from an input with no autocomplete attribute to one with autocomplete="off"
(3) The autocomplete="off" setting is ignored.
What is the expected result?
When navigating back to input #1 from input #2 there should be no autocomplete.
What happens instead?
The autocomplete appears on the keyboard when going from input #2 to input #1.
,
Apr 27 2016
The same behavior exists with autocapitalize attribute. input 1 <input type="text" autocapitalize="words"> input 2 <input type="text"> input 3 <input type="text" autocapitalize="words"> going from input #2 to input #1 results in no autocapitalization. Going from input #3 to input #1 results in autocapitalization again.
,
Apr 28 2016
,
May 5 2016
Still happens in 50.0.2661.89 (Official Build) (32-bit) on android 6.0.1 Blink: 537.36
,
Jul 19 2016
,
Jul 20 2016
I'll try to repro
,
Jul 28 2016
I experienced the same problem on Android 4.4.2 with Chrome/51.0.2704.81 The problem only occurs when the keyboard stays open between the switching of input-fields. When the next field is selected the keyboard seems to use the keyboard-settings of the previous input-field. Small example: #1: <input type="text" autocapitalize="words"> #2: <input type="text" autocapitalize="none"> #3: <input type="number"> When #1 is focused the keyboard pops up and works as expected. Going to #2 keeps the keyboard in autocapitalization. Switching back to #1 again results in the keyboard without autocapitalization Going to #2 again puts the keyboard in autocapitalization. If, after this, input #3 is focused you'll see that the keyboard switches to autocapitalize="none" first for a short time before switching to a numeric keyboard. I tested this with multiple keyboards and they all seem to experience this problem.
,
May 1 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mfa...@usinternet.com
, Apr 27 2016