Closed
Bug 1919281
Opened 1 year ago
Closed 1 year ago
[PL][allegro.pl] Form autofill/preview/clear aren't applied on the level 2 and level 3 of the address
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
VERIFIED
FIXED
139 Branch
People
(Reporter: hyacoub, Assigned: theidkamp)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [fxcm-addr-compatibility])
Attachments
(3 files)
Found in
- Nightly 132.0a1
Affected versions
- Nightly 132.0a1
Tested platforms
- Affected platforms: macOS 14.2.1
Preconditions
- Have at least one address saved
- locale build: PL
- Preferences:
browser.search.region
extensions.formautofill.addresses.experiments.enabled - true
extensions.formautofill.addresses.supportedCountries - PL
extensions.formautofill.addresses.capture.requiredFields empty/blank
Steps to reproduce
- Reach the address form on https://www.allegro.pl
- Check autofill/preview/clear functionality on the address fields
Expected result
- Form autofill/preview/clear should be applied on the eligible fields
Actual result
- Form autofill/preview/clear aren't applied on the level 2 and level 3 of the address
Regression range
- N/A
Additional notes
- Not reproducible on Chrome.
- Fathom: https://drive.google.com/file/d/1cZsc5m3Pq41fcuT7iTG8Og2BGH3kugX7/view?usp=sharing
Updated•1 year ago
|
Type: defect → task
Updated•1 year ago
|
Severity: S4 → N/A
Priority: -- → P3
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Whiteboard: [fxcm-addr-compatibility]
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → theidkamp
| Assignee | ||
Comment 2•1 year ago
|
||
Pushed by theidkamp@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6d855bbf3b51
Adapting Expressions to match housenumber and apartment field in polish. r=dimi
Comment 4•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox139:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
Comment 5•1 year ago
|
||
Verified in Nightly 139.0a1 (2025-04-07) and the issue described is now fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•