Closed
Bug 1496069
Opened 6 years ago
Closed 6 years ago
Editing the Saved Addresses shows red fields
Categories
(Toolkit :: Form Autofill, defect, P1)
Tracking
()
VERIFIED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox62 | --- | unaffected |
firefox63 | --- | verified |
firefox64 | --- | verified |
People
(Reporter: david.olah, Assigned: MattN)
References
Details
(Keywords: regression, Whiteboard: [webpayments])
Attachments
(2 files)
15.45 KB,
image/png
|
Details | |
46 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-release+
|
Details | Review |
[Affected versions]: Nightly 64.0a1 (2018-10-02), Firefox 63.0b11 [Affected platforms]: Platforms: Windows 10, Mac OS X, Ubuntu 16.04. [Preconditions]: Modify the following prefs via about:config: - extensions.formautofill.available: on - extensions.formautofill.creditCards.available: true [Steps to reproduce]: 1. Go to about:preferences#privacy and search for Forms & Passwords 2. Check the Autofill addresses and click the Saved Addresses button 3. Add a new address with a name 4. Select the same address and hit the Edit button [Expected result]: - The uncompleted fields are not highlighted with red border. [Actual result]: - The uncompleted fields are highlighted with red border (if you change the name, the rest of the fields remain red but the form can be saved.)
Assignee | ||
Comment 1•6 years ago
|
||
The change at https://hg.mozilla.org/mozilla-central/diff/4b668c00c226/browser/extensions/formautofill/content/manageDialog.js was just wrong. The 4th argument is for a closing callback.
Blocks: 1427961
status-firefox62:
--- → unaffected
status-firefox-esr60:
--- → unaffected
Keywords: regression
Priority: -- → P2
Whiteboard: [webpayments]
Updated•6 years ago
|
Flags: qe-verify+
QA Contact: hani.yacoub
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → MattN+bmo
Status: NEW → ASSIGNED
Priority: P2 → P1
Assignee | ||
Comment 2•6 years ago
|
||
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/autoland/rev/d71434f40755 Properly pass noValidate to EditAddress and set @novalidate. r=jaws
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d71434f40755
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Assignee | ||
Comment 5•6 years ago
|
||
Comment on attachment 9017400 [details] Bug 1496069 - Properly pass noValidate to EditAddress and set @novalidate. r?jaws [Beta/Release Uplift Approval Request] Feature/Bug causing the regression: Bug 1427961 User impact if declined: Users won't be able to save corrections to saved addresses if they are missing some "required" fields Is this code covered by automated tests?: Yes Has the fix been verified in Nightly?: No Needs manual test from QE?: Yes If yes, steps to reproduce: Ensure that editing a record with some missing fields doesn't show the red outlines and that the save button is enabled. List of other uplifts needed: None Risk to taking this patch: Low Why is the change risky/not risky? (and alternatives if risky): Fairly straightforward change to pass an additional dialog argument and fix setting the attribute String changes made/needed: None
Attachment #9017400 -
Flags: approval-mozilla-beta?
Comment 6•6 years ago
|
||
Comment on attachment 9017400 [details] Bug 1496069 - Properly pass noValidate to EditAddress and set @novalidate. r?jaws Resetting the uplift request flag for approval‑mozilla‑release as we are now in the release candidates phase Matt, are the flag changes needed to reproduce the issue in comment #0 a supported scenario on our release channel or would one hit this bug only if he changed values in about:config? [Beta/Release Uplift Approval Request] Feature/Bug causing the regression: None User impact if declined: Is this code covered by automated tests?: Yes Has the fix been verified in Nightly?: Yes Needs manual test from QE?: Yes If yes, steps to reproduce: List of other uplifts needed: None Risk to taking this patch: Low Why is the change risky/not risky? (and alternatives if risky): String changes made/needed:
Attachment #9017400 -
Flags: approval-mozilla-beta? → approval-mozilla-release?
Comment 7•6 years ago
|
||
Verified as fixed on Firefox Nightly 64.0a1 on Windows 10 x 64, Windows 7 x32, Mac OS X 10.13 and on Ubuntu 16.04 x64.
Updated•6 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 8•6 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #6) > Matt, are the flag changes needed to reproduce the issue in comment #0 a > supported scenario on our release channel or would one hit this bug only if > he changed values in about:config? Neither of those prefs need to be changed to hit this bug in en-US builds for users in the US where Address Autofill is enabled by default.
Comment 9•6 years ago
|
||
Comment on attachment 9017400 [details] Bug 1496069 - Properly pass noValidate to EditAddress and set @novalidate. r?jaws Taking for RC2 as this is a visible UI regression for a feature affecting our top locale and it was verified as fixed on Nightly.
Attachment #9017400 -
Flags: approval-mozilla-release? → approval-mozilla-release+
Comment 10•6 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-release/rev/c023e8e06880
Comment 11•6 years ago
|
||
This got backed out after there were conflicts applying the patch and there were eslint and browser-chrome failures after resolving: https://hg.mozilla.org/releases/mozilla-release/rev/e986b9e437b6859ca180861e5fa265081b2d12cc Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&resultStatus=usercancel%2Crunnable%2Ctestfailed%2Cbusted%2Cexception%2Cretry&group_state=expanded&selectedJob=206369237&revision=8c489cac4a10cb54027647e64cfd08cff46bef37
Flags: needinfo?(MattN+bmo)
Assignee | ||
Comment 12•6 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-release/rev/b9768ea75a5d
Assignee | ||
Comment 13•6 years ago
|
||
eslint and autofill tests passed locally.
Flags: needinfo?(MattN+bmo)
Comment 14•6 years ago
|
||
Build ID: 20181018182531 User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Verified as fixed on Firefox 63.0 RC build 2 on Windows 10 x 64, Windows 7 x32, Mac OS X 10.13 and Ubuntu 16.04 x64.
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•