Dynamic Form Support
Categories
(Toolkit :: Form Autofill, enhancement, P2)
Tracking
()
People
(Reporter: dimi, Assigned: janika)
References
(Blocks 10 open bugs, Regressed 3 open bugs)
Details
Attachments
(7 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Updated•2 years ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 1•7 months ago
|
||
Sets up two observer types in order to detect dynamic form changes:
1. MutationObserver for an address/cc form (document if form-less),
observing node additions or removals in the form's node subtree
2. IntersectionObserver for each invisible elements in an address/cc form (document if form-less),
observing intersections (threshold 1) between the invisible element and the form/document
A "form-changed" event gets dispatched in the observers' callback functions when the fields that were added/removed (MutationObserver)
or became visible (IntersectionObserver) are of address or cc type. When the FormAutofillChild receives a "form-change" event it
compares the previous formDetails with the formDetails after the form change. If they differ, the FormAutofillChild sends the message
"FormAutofill:onFieldsDetected" to the FormAutofillParent, which triggers the form detection process in all children.
In onFieldsDetectedComplete the form handler's elements are updated accordingly to the new set of elements.
Updated•7 months ago
|
Updated•7 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Comment 2•6 months ago
|
||
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Comment 3•6 months ago
•
|
||
Hey @owlish, my patch is currently blocked by geckoview-reviewers
group. I'd appreciate if you or someone from your team could give a quick review on patch P1. It's only adding a new event to FormAutofillChild in mobile/shared/chrome/geckoview/geckoview.js
. Thank you!
Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Comment 4•6 months ago
|
||
If a form change occurs immediately after an initial autocompletion process, the FormAutofillChild notifies the
parent to re-trigger another filling process in all children to fill the fields that were added or became
visible on form change. Only form changes occuring within the threshold FormAutofill.fillOnDynamicFormChangesTimeout
(default is 500ms) also lead to another filling process.
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Comment 5•6 months ago
•
|
||
@owlish, thank you for the review on P1!
Assignee | ||
Comment 6•6 months ago
|
||
Updated•6 months ago
|
Assignee | ||
Comment 7•6 months ago
|
||
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Comment 9•5 months ago
|
||
Assignee | ||
Comment 10•5 months ago
|
||
The problem is that when calling triggerAutofillActionInChildren
in onFillOnFormChange
we need to pass the fieldDetails of section.getAutofillFields()
instead of the section
.
Comment 11•5 months ago
|
||
Comment 12•5 months ago
|
||
Backed out for causing failures at browser_form_changes.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/b1ee17fc754b8e0393eeeb75a5d363968d80982e
Failure log: https://treeherder.mozilla.org/logviewer?job_id=496741897&repo=autoland&lineNumber=15543
Assignee | ||
Comment 13•5 months ago
|
||
Updated the patches and fixed failures for browser_form_changes.js
.
Try run without failures: https://treeherder.mozilla.org/jobs?revision=e7c7a8bc0c2861aaf4bfbd5bfc86c8c251a94f73&repo=try
Comment 14•5 months ago
|
||
Comment 15•5 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8ec644ecbdc4
https://hg.mozilla.org/mozilla-central/rev/730834404aec
https://hg.mozilla.org/mozilla-central/rev/1cad27d93ad4
https://hg.mozilla.org/mozilla-central/rev/3a970dd4c57e
https://hg.mozilla.org/mozilla-central/rev/e88442d8bd32
Comment 16•5 months ago
|
||
This lead to a 5.6KB regression in installer size on Windows. This small increase is below any alertable threshold, so consider this comment only as a FYI
Assignee | ||
Comment 17•5 months ago
|
||
- Adds two events in formautofill/metrical.yaml: filledOnFieldsUpdateAddressForm and filledOnFieldsUpdateCcFormV2
that record the filling state of a form after the second autofill action and which fields were filled after the update. - Adds test cases in browser_dynamic_form_telemetry.js
- Renaming all dynamic form related test files to follow the same name pattern
Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Comment 18•5 months ago
|
||
Comment 19•5 months ago
|
||
bugherder |
Comment 20•5 months ago
|
||
:janika did you want to include this in the 138 release notes?
Also, should we change this to an enhancement instead of a task?
Assignee | ||
Comment 21•5 months ago
|
||
Yes, I changed it from task to enhancement.
:janika did you want to include this in the 138 release notes?
I'll get back to you on this tomorrow! Thanks for asking!
Assignee | ||
Comment 22•5 months ago
|
||
Updated•5 months ago
|
Comment 23•5 months ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Comment 24•5 months ago
|
||
Comment 25•5 months ago
|
||
bugherder |
Assignee | ||
Comment 26•4 months ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Increases user convenience when autofilling address and credit card forms
[Affects Firefox for Android]: Yes
[Suggested wording]: Improves Address Autofill and Credit Card Autofill experience by ensuring that forms adjusting dynamically as users fill them are properly supported. This includes cases where fields appear or change based on input - such as selecting a country - so that newly revealed fields are now filled as expected.
Comment 27•4 months ago
|
||
Added to the 138 release notes with slightly altered wording.
https://www.mozilla.org/en-US/firefox/138.0a1/releasenotes/
Assignee | ||
Updated•3 months ago
|
Description
•