User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

I do know why this has been separated from the regular syncing process. It doesn't make sense.

It's annoying to redo what we have done all over again and again.
Firefox remembers which extensions are installed but doesn't remember which shortkeys a user has assigned.

If I select prevent accessibility services, next time I install Firefox, you have to select that manually.

If the user customizes their browser in certain or any pattern, Firefox doesn't sync that pattern.

I don't know why "syncing abilities" are so minimized at such a poor level.
The whole idea of "start from where you left" concept lacking here.

God bless Mozilla.

I'm setting the component in order to involve the development team to review this enhancement.

Hi Pranav,

We're sorry that Sync has let you down here. There's a long tail of things we don't sync, some intentional, others because we haven't thought the user experience through yet. Responding to your questions inline:

Firefox [...] doesn't remember which shortkeys a user has assigned.

I think this is bug 1438776.

If I select prevent accessibility services, next time I install Firefox, you have to select that manually.

This is the accessibility.force_disabled pref. Syncing it by default could possibly be unexpected—you might want to use accessibility services on one device, but not others, for example. For now, you can sync it as a custom preference by following the instructions to add a services.sync.prefs.sync.accessibility.force_disabled Boolean pref in about:config.

If the user customizes their browser in certain or any pattern, Firefox doesn't sync that pattern.

That is bug 943182.

Given the links above to existing bugs on file, I'm going to close this one as a duplicate. Thanks again for the feedback!