I'm happy to announce that the Sync work for formautofill has landed \o/
Hat-tip to Kit and Thom in particular from the Sync team, and Matt, Luke
and Sean from the autofill team for pulling this off.
* In new Nightlies, there are 2 new preferences,
`services.sync.engine.addresses.available` and
`services.sync.engine.creditcards.available`, with default values of
`false`. At least one of these needs to be set to `true` to see any
changes - in other words, by default, these new engines are not visible
in any way. Bug 1382530 is to default these preferences to true once we
get QA signoff.
Important Note: As implied above, there are 2 distinct preferences used
by each of these new engines - one which indicates of the engine is
*available*, and the other which indicates if the engine is *enabled* -
these are 2 distinct states but possibly easy to confuse. If the
.available pref is set to false, the engines will not be exposed in any
UI and not used at all. However, even once these engines have been made
available it is possible they will not be *enabled*. The available pref
has no UI, while the the enabled state is managed by checkboxes in
about:preferences#sync.
Also Note: You must use about:config to adjust these .available
preferences, and you should restart the browser after toggling them.
One these .available prefs have been set to true:
* Existing sync users: about:preferences#sync will then offer the new
engines, but their default value is disabled - ie, existing Sync users
will need to flip the .available preferences to true *and then* visit
about:prefs#sync to enable the engines. I believe work is planned by the
autofill team so that the doorhangers will also allow existing sync
users to enable the engines without explicitly visiting
about:preferences, but I'm not aware of the status of that work.
* New sync uses: Once these new .available preferences have been
toggled, creating a new account will offer these new engines. Note that
there is a bug - the new engines default to disabled whereas they should
default to enabled for new accounts. I opened
https://github.com/mozilla/fxa-content-server/issues/5269 to track this.
This profile is now configured. For testing purposes:
* On another desktop profile connected to the same Sync account (or
another new desktop profile you connect to the same account), change the
`services.sync.engine.addresses.available` preference to true, restart,
then sync - you should find the engine becomes automatically enabled on
this profile due to it being enabled on the initial profile.
* Addresses should sync - additions should be available on both
profiles, deletions should be mirrored, and conflicting changes should
cause a "fork" (ie, 2 similar address records will exist) of a record.
* Bug 1382530 is to flip these .available preferences to true by
default. It sounds like we expect only .addresses to be made available
in the first instance, so we might want to split that bug, but we should
do that as soon as QA/testing indicates it meets our quality bar.
* The sync team has no further work on this identified (obviously other
than bugs found during testing) - so please reach out to us if there is
additional work you expected to be done by us as we aren't currently
planning for it!
* I believe we can now throw this to the Softvision wolves for in-depth
testing :)
Thanks all!
Mark
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
