1819691 - [CA][movieposters.com] The autofill and clear form dropdowns are displayed only for the Email field

Status: VERIFIED FIXED

(Toolkit :: Form Autofill, defect, P3)

Description

[Anca Soncutean, Desktop QA]

Attachment: screencast issue - movieposters.com.gif

Found in

• 112.0a1

Affected versions

• 112.0a1, 111.0b7, 110.0.1

Affected platforms

• Windows 10, macOS 13

Preconditions

• browser.search.region set to CA
• have a locale CA (en-ca) build
• have at least one address saved in about:preferences#privacy

Steps to reproduce

1. Reach the Address form on https://www.movieposters.com/
2. Click in the Name fields, Address, City, etc.
3. Click in the Email field
4. Hover over any saved address entry and observe the autofill preview behavior
5. Select 1 saved address entry

Expected result

1. The autofill dropdown should be displayed for all eligible fields.
2. The preview should be properly done for all the eligible fields.
3. All the fields should be auto-filled with accurate data.

Actual result

1. The autofill dropdown is displayed only for the Email field.
2. Only the Email field is previewed.
3. The clear form dropdown is displayed only for the Email field.

Regression range

• Not a recent regression.

Additional notes

• Not reproducible in Chrome.

Comment 1

[Alin Ilea, Desktop Test Engineering]

Attachment: 2023-05-26_13h33_40.mp4

The autofill dropdown is displayed accordingly for all the fields now and all the fields are autofilled correctly.
Note: When the fields are autofill from the Email fields, the Autofill dropdown is displayed instead of the Clear Form dropdown for all the fields except the Email field.

Comment 2

[Alin Ilea, Desktop Test Engineering]

Fathom Fox Sample: https://drive.google.com/file/d/1Un1nMDSnZsviY0Y0SVvCy2e0NWW-LW6L/view?usp=share_link

Comment 3

[Dimi Lee [:dimi]]

Our heuristic identified two section for this address form. First section is "email" + some hidden address fields. And the second section is fields under "Shipping address".
There are two possible solution for this issue

1. Figure out why our checkVisibility API consider hidden elements as visible.
2. Since the hidden elements has aria-hidden attribute, we can also filter out fields that are not focusable when autofilling

Comment 4

[Alin Ilea, Desktop Test Engineering]

Attachment: 2023-06-19_13h50_55.mp4

The shipping address section fields are autofilled correctly now, but if the autofill is triggered from the email field, the autofill dropdown is displayed for the address fields instead the clear form dropdown. If the autofill is triggered from a Shipping address section field, the clear form dropdown is displayed accordingly for all fields, but the email field is not autofilled.Verified in the latest Nightly 116.0a1 (2023-06-19).

Comment 5

[Dimi Lee [:dimi]]

(In reply to Alin Ilea, Desktop QA from comment #4)

The shipping address section fields are autofilled correctly now, but if the autofill is triggered from the email field, the autofill dropdown is displayed for the address fields instead the clear form dropdown. If the autofill is triggered from a Shipping address section field, the clear form dropdown is displayed accordingly for all fields, but the email field is not autofilled.Verified in the latest Nightly 116.0a1 (2023-06-19).

This page has two address sections, one is "email" + some hidden address fields, another is the country field and fields after the country field.
When the autofill is triggered from the email field, we filled into those hidden fields as well (Somehow those fields are not consider invisible by the checkVisibility API). And after we fill into those hidden fields, the website itself handles populating the value just filled into to those visible fields. This is why it looks like we autofill all the fields together. So the reason that we don't show the "clear Form" button when clicking on fields other than email field, is because those fields are not autofill by us.

Note. I observe the same behavior in Chrome as well.

Comment 6

[Dimi Lee [:dimi]]

Close this bug based on Comment 4.

Comment 7

[Anca Soncutean, Desktop QA]

I verified this issue once again just to be on the safe side that no regression was introduced since Alin's verification. I have the same behavior mentioned by him on the latest Nightly (117.0a1 - 2023-07-19). But based on comment 5 I will close this issue as verified fixed.