1683413 - online.adp.com/ipay/login.html LOGIN button is not clickable until extra characters are appended to filled password

Status: RESOLVED WORKSFORME

(Toolkit :: Password Manager: Site Compatibility, defect, P3)

Description

[Chris Peterson [:cpeterson]]

Steps to reproduce

0. Have a saved username and password for ADP iPay.
1. Load https://online.adp.com/ipay/login.html.
2. The "USER ID" field is auto-filled with my saved username.
3. Click the password field and select the saved account name from the form fill menu. (That the "PASSWORD" field is not auto-filled is bug 1188733. I don't know if these problems are related.)
4. The password field is filled with my saved password.
5. Try to click the "LOGIN" button.

Expected result

The LOGIN button is blue and clickable. Clicking it logs you into the site.

Actual result

The LOGIN button is grayed out and not clickable.

I have to click focus into the PASSWORD field, append an extra character to the filled password, and then delete the extra character before the LOGIN button turns blue and is clickable.

See also bug 1618937 where a site's login button is not clickable until user clicks focus to already-populated password field. That bug, however, only requires a focus event on the password field, while this bug requires character input events in the password field.

Comment 1

[Chris Peterson [:cpeterson]]

Attachment: Login debug messages logged to Browser Console.txt

Comment 2

[Dimi Lee [ooo 16.04 - 21.04］]

It looks like this website listens to key up/down to change the state of the LOGIN button.
Chrome doesn't have this issue because Chrome fires focus, blur, key up and key down when auto fill. See here.

Comment 3

[Sam Foster [:sfoster] (he/him)]

There is discussion on what the correct browser behavior should be in this case at https://github.com/whatwg/html/issues/3016
Anything we do to address this bug should be informed by a decision on that standards issue.

Comment 4

[Chris Peterson [:cpeterson]]

I don't know if Firefox changed or ADP's login page changed, but I can no longer reproduce this bug.