To be clear: this is only true if you enable sync for extensions.  If you just don't sync extensions, different devices can always have different enabled/disabled states.

We've discussed this before, and unfortunately, there's no good way of introducing a per-device, per-extension enabled/disabled state without either breaking current use sync use cases or introducing a very complicated UI.  My suspicion is that we won't want to do this, but over to jawag@ for any more input.

I never considered stopping sync of extensions (nor realized that was possible). Not ideal but it could be a partial solution.

Yeah, sync can be disabled on a per-component basis.  So you can continue syncing e.g. history and bookmarks, but not sync extensions.  That's usually enough to handle most use cases, and already has a defined UI.  There's been little appetite for complicating that UI (and the underlying sync code) by adding "sub categories" so that you could e.g. sync extension storage, but not extension enabled state, etc.

Agree with rdevlin's comments. carlosk, closing this bug for now but please let us know if disabling extensions sync isn't a sufficient solution, and if so, why. Thanks!