Steven, please triage. Thank you!

Is this new behavior? Does it matter whether it is set in old settings: chrome://settings-frame?

If it's a behavior change it will require more than just a Settings UI change and should probably be owned by somebody familiar with the pref (if available) or added to a feature triage pool.

Both of my user accounts have "Swap primary mouse button" checked at chrome://settings-frame. I suspect that this is unrelated to MD settings and has never worked.

tbuckley@, kusher@ - WDYT, should we make 'Swap primary mouse buttons' a device setting? Or device owner setting?

What do we do for display settings (e.g. layout, orientaton, etc)?

I would expect that setting to follow whatever pod is selected just like wallpaper and a11y settings do.

"pod" ?

Do you mean that if the user selects a profile in the login screen, the mouse buttons would then swap?

Yes. (Pods are users on the login screen.)

re: #7, yes. That's my initial thought. We currently do that with things like key repeat rate, etc.

Mouse button swap requires more thought tho. Every option I can think of is really bad in some way.

This is more than a UI change and requires some design thought.

-> abodenha@ to triage and reassign.

Assigning to Zach to prioritize.

@Maria, this is a tricky interaction design question, would you mind taking a look?

The only reasonable thing I can think of is respecting the device owner's setting exclusively. Anything else involves swapping the function of mouse buttons based on which pod is currently selected, which seems like a usability nightmare. 

+1 to respecting owner's setting. Only other option I could see is remembering the last signed-in user's setting.

One we define this, we should:
1) Apply the same logic to Guest Mode (i.e. primary mouse button will be the same on login screen and Guest Mode)
2) Do a quick audit of settings to see if any other settings should be preserved on sign-in screen / Guest Mode.

Yeah, I agree with using the owner setting. It will not be ideal for users on shared devices but my guess is that it's a limited group of users who changes this, and the intersection of that group and the group where the device owner is someone else is even smaller so it seems okay. 

I'm not sure about the Guest mode case. I get the "consistent with sign in screen" argument but I've always thought of Guest mode as more of a vanilla default experience. What are some of the benefits of keeping the setting for Guest mode?

Marking as P3 available feature for future consideration.

P3 is where bugs go to languish forever. Please either triage this or WontFix it if it's never going to be fixed.

Bulk-assigning unassigned status area bugs to me.