This is an enhancement request to the form data sync engine to also include the meta data required to support awesome form fill. In talking to Ed, there isn't an API that we can use to get/set this information. We could propose one and implement it in weave, but should get dolske involved.

We probably don't want to propose an API and implement it. That feels like overkill, and we should just have the right people implement that API in core (we need it there anyway). That said, we could monkeypatch this with raw SQL, if we felt like it was really important, but that feels like a path to disaster. I think this is 3.6+ only, so that gets more prone to fun corner cases. Without a burning need to do this now, my best put that we continue to live with the less-awesome version of form history for sync (Firefox has this issue) until there's a sane API, and then only use that API. In the long view (sync as a core component) this gets us where we need to go, without burning resources on an interim solution.

Awesome form fill isn't a thing any more. There is work being done on "addresses", which is similar and will be synced, so closing this one.

Mark, I think this bug is talking about syncing the form history metadata fields that affect form history frecency: * timesUsed * firstUsed * lastUsed That isn't going anywhere and will continue to be used on forms and fields where Form Autofill can't help.

Thanks for the clarification