Undo the FormHandler integration with the FormHistoryChild
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: janika, Assigned: janika)
References
Details
(Whiteboard: [fxcm-addr-compatibility] )
Attachments
(1 file)
FormHistory is currently not compatible with how the FormHandler is listening to form submissions so we are undoing the FormHandler integration in FormHistory from Bug 1881501.
Why?
The FormHandlerChild starts listening to form submission after it is created. But Bug 1884632 changes when the FormHandlerChild is created.
Now the FormHandlerChild is created when the FormAutofillChild or the LoginManagerChild register their interest in form submissions.
This means FormHistoryChild would need to register its interest as well, thus it needs to exist before the form submission occurs. And this causes a problem. Because in some cases, the FormHistoryChild doesn't exist before the form submission, so it cannot register its interest in time. Before introducing the FormHandler in Bug 1881501 the form submission was what created the FormHistoryChild and let it capture the submitted values.
This incompatibility could cause the FormHistoryChild to miss form submissions.
That's why we let the FormHistoryChild to directly listen for DOMFormBeforeSubmit again.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Backed out for causing gv-junit-fis failures
Comment 6•1 year ago
|
||
bugherder |
Description
•