I agree with Emily that using a system autofill provider to fill web forms in Fenix isn't going to work well for the reasons she outlined and it won't work nearly as well as the Toolkit password manager that was used in Fennec.
(In reply to Vlad Filippov (:vladikoff) from comment #1)
Yes, without knowing anything about Geckoview parts..... what we CAN do is build a webextension and borrow the magical browser.js from Fennec, which does form detection for usernames and passwords and do autofill that way.
Please do not fork the toolkit login hueristic code like Fx iOS did… we still haven't unforked it and iOS has missed out on various improvements over the last few years as a result.
Ideally this would be properly supported in GeckoView like it was in Fennec, sharing the toolkit code.
(In reply to Chris Peterson [:cpeterson] from comment #3)
Fenix meta issue for login management: https://github.com/mozilla-mobile/fenix/issues/1284
Management and autofill are very different problems btw.
(In reply to Chris Peterson [:cpeterson] from comment #4)
WONTFIX because snorp says GV already has the necessary API: GV's SessionTextInput API. For Android O+ you would still probably want to use a system autofill provider. Perhaps A-C can create an autofill abstraction for Fenix that encapsulates both GV's SessionTextInput API and Oreo's autofill API, depending on the OS version at run time?
Having to re-implement all of the toolkit password manager heuristics in Fenix seems like the wrong approach to me. Exposing the existing toolkit password manager would give much better results.
This issue was about fill but the equally important part of the equation is capture and I don't believe GV has support for that yet… i.e. saving password from registration or change forms. A browser password manager that only fills but doesn't save isn't very helpful.