There's not a perfect mapping right now. See SessionController::GetLoginStatus().
We need to handle owner vs. non-owner users and the "adding secondary user" state.
xiyuan, do you want to own this, or should I keep it?
I will take the chance to consolidate the LoginStatus code path:
- Make cash/mash use the same code path for LoginStatus update;
- Migrate ash code to use only SessionController::GetLoginStatus;
Comment 1 by xiy...@chromium.org
, Mar 27 2017Owner: xiy...@chromium.org