[US][www.walmart.com] The Clear Autofill form dropdown menu is misplaced for the autofilled fields
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
People
(Reporter: epopescu, Assigned: joschmidt)
References
(Blocks 1 open bug, Regressed 1 open bug, )
Details
(Whiteboard: [fxcm-addr-compatibility] )
Attachments
(3 files)
Found in
- Nightly 118.0a1
Affected versions
- Nightly 118.0a1
Tested platforms
- Affected platforms: Windows 10 x64
Preconditions:
- Set browser.search.region to US in about:config
- Save 1 or 2 addresses in about:preferences#privacy, Forms & Autofill section
- Use US VPN
Steps to reproduce
- Go to https://www.walmart.com/
- Add one item to cart and proceed to checkout
- Use autofill feature in the Shipping address form by clicking inside any field
- Click again in the field previously autofilled to display the Clear Autofill form dropdown
Expected result
- The Clear Autofill form dropdown is displayed under the autofilled field where user previously clicked in.
Actual result
- The Clear Autofill form dropdown is misplaced under the Phone number field.
Regression range
- N/A
Additional notes
- The issue can not be reproduced in Google Chrome.
- Fathom Fox page
Reporter | ||
Updated•2 years ago
|
Updated•1 year ago
|
A race condition has caused the wrong input element to be set as the
active, focused one when a script on a website reacts to autocomplete
inputs and manipulates the inputs. This happened because the
FormFillController listens for changes to the attributes of the input
elements, and then restarts itself delayed. This overwrote the focus
that had been set correctly in the meantime. This patch cancels this
restart when a new element is set as focus.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Backed out for causing leakcheck failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/13a974284e8fde0697f45ce14f1b344cb31e1a25
Failure log: https://treeherder.mozilla.org/logviewer?job_id=458112718&repo=autoland&lineNumber=8091
Comment 6•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f0d88c071cf9
https://hg.mozilla.org/mozilla-central/rev/1f668a12c776
Updated•1 year ago
|
Updated•1 year ago
|
Reporter | ||
Comment 7•1 year ago
|
||
I've replicated this issue using Nightly 118.0a1 on Windows 10 x64.
Verified as fixed in the latest Nightly 128.0a1 version on Windows 10 x64, macOS 11, and Ubuntu 22.04, as the issue no longer occurs.
Description
•