Closed
Bug 1819983
Opened 1 year ago
Closed 26 days ago
[CA][burtsbees]State values are not previewed as filled in (data and yellow highlight), nor autofilled
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: epopescu, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Found in
- Nightly 112.0a1
Affected versions
- Nightly 112.0a1
- Firefox 110.0.1
- Firefox 111.0b7
Tested platforms
- Affected platforms: Windows 10, macOS 13, Ubuntu 22.04
- Unaffected platforms: none
Preconditions
- Install the Firefox en-CA build
- Set browser.search.region to CA in about:config
- Save 1 or 2 addresses in about:preferences#privacy, Forms & Autofill section
Steps to reproduce
- Go to https://www.burtsbees.com/
- Add one item to cart
- Proceed to checkout
- Click in any eligible field and use autofill feature to preview and autofill the eligible fields
- Observe the State field
Expected result
- State values are previewed as filled in (data and yellow highlight) and autofilled and highlighted upon selection.
Actual result
- State values are not previewed as filled in (data and yellow highlight) and autofilled and highlighted upon selection.
Regression range
- Not a recent regression.
Additional notes
- The issue is reproduceable in Google Chrome.
Reporter | ||
Updated•1 year ago
|
Blocks: formautofill-compatibility
Severity: -- → S3
Has STR: --- → yes
status-firefox110:
--- → affected
status-firefox111:
--- → affected
Depends on: 1755033
Comment 1•1 year ago
|
||
:epopescu, if you think that's a regression, could you try to find a regression range using for example mozregression?
Updated•1 year ago
|
Priority: -- → P3
Reporter | ||
Comment 2•2 months ago
|
||
I've retested this issue in Nightly 125.0a1 (2024-03-04) on Windows10 x64 given that Bug 1755033 has been RESOLVED FIXED.
The issue persists in the latest Nightly 125.0a1 version.
Attached screen recording.
Comment 3•26 days ago
|
||
The state field isn't a real <select> element so we can't autofill it.
Comment 4•26 days ago
|
||
Based on Comment 3 and this issue is reproducible in Chrome, close this bug as WON'T FIX
Status: NEW → RESOLVED
Closed: 26 days ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•