Why is this restrict view?

IIRC this is normal behavior.

Ok, definitely not normal.  

Zach, is this not expected behavior?

I've been trying to track down the exact logic we're using for warm welcome triggering to no avail. Rahul could someone from your team find that code?

Regardless though, this sometimes triggers when Chrome Sync is being particularly flaky, we should investigate that further.

This does look like normal behavior.

If a user has already logged onto a Chromebook (i.e., already exists in the user list), we show the user as new (there are checks several places for this). The feedback report isn't talking about that case.

This is for the case where a user has logged on to 'another' Chromebook. Do we even sync that as a preference? Adding Alexander and Jacob in case they know of any such preference.


Assigning to Zach to prioritize as a feature instead once Jacob/Alex confirm.

It seems like there are a couple possible situations this bug could describe:

First, assume that I have a chromebook and have signed into multiple users.

1: I buy a new chromebook, I expect oobe/gaia to suggest who I am. This may be technically possible with some sort of easy-unlock style solution, but as far as I understand nothing is available for this consumer-side (ie, pre-enrolling the device at the factory for enterprise).

2. I buy a new chromebook and sign in using one of the users I signed into the previous chromebook with. I expect to see the other signed in users from the previous chromebook as well. I'm unaware of any existing work towards enabling this.

It seems like both situations will have fundamental privacy concerns as well.

 abodenha@, do you have any more context on this being "definitely not normal"?

I don't recall why I made comment 4.  Everything I'm seeing here says this is WAI.