1663866 - [Yahoo.com] First/Last Name field inputs are not captured and passed over to the doorhanger as a suggestions

Status: RESOLVED INVALID

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

Description

[Andrei Purice]

Attachment: yahoo.com.mp4

Affected Versions:
All - where V2 doorhanger is enabled by default or force enabled.

Tested on:
Windows 10/7
MacOS 10.13
Ubuntu 20.04.1

Steps to Reproduce:

1. Reach Yahoo.com Register Form.
2. Fill in all the fields and click on the grey key icon to see the dismissed doorhanger or submit the form.
3. Click on the dropmarker from the username field and check the suggested username list.

Expected Result:
The values from the "First/Last Name" should be captured and passed over to the doorhanger as a suggestions.

Actual Result:
All other values are displayed in the list.

Regression-Range:
Not a regression, seems like a site issue. However, Chrome does capture the "First/Last Name" field values.

Severity SUggestion:
S4 - since the First/Last Name values are not relevant for saving credentials given the Login form requires the email address of the user.

Notes:
Field attributes for First Name:
<input type="text" id="usernamereg-firstName" class="ureg-fname input-with-icon icon-name " autocomplete="given-name" name="firstName" placeholder="First name" aria-label="First name" value="" maxlength="32" aria-required="true" aria-invalid="false">
For Last Name:
<input type="text" id="usernamereg-lastName" class="ureg-lname " name="lastName" autocomplete="family-name" placeholder="Last name" aria-label="Last name" value="" maxlength="32" aria-required="true" aria-invalid="false">

Comment 1

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

This is expected behavior. We don't consider the first/last names fields as candidates for the username - correctly in this case.
This might be a valid bug if our guess there was wrong and those fields should have been candidates.