New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 632866 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 632275



Sign in to add a comment

Don't allow creation of a Supervised User with a blank name on ChromeOS

Project Member Reported by pam@chromium.org, Jul 29 2016

Issue description

By  issue 632275 , a SU can be created with an empty name on Chrome OS, but not on any other desktop platform. We should prevent that everywhere.
 

Comment 1 by treib@chromium.org, Aug 3 2016

Cc: treib@chromium.org bauerb@chromium.org atanasova@chromium.org
Owner: ----
Status: Available (was: Assigned)
I doubt I'll get to this any time soon, so throwing back into the "available" pool. Also I'm not sure this is a P1? (Assuming the crash gets fixed)

Comment 2 by treib@chromium.org, Aug 3 2016

In the SU creation dialog, the "Next" button does get disabled if you don't enter a name, but double-tapping on the camera icon triggers creating the SU even without a name.

Comment 3 by pam@chromium.org, Aug 3 2016

Wow. OK, that's pretty obscure.

I do think it's a P1 anyway, since it results in making a broken SU, i.e. one that can't be imported onto another device. Although if it turns out to be unexpectedly hard to fix, that might change.
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 3 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by treib@chromium.org, Aug 3 2017

Status: WontFix (was: Untriaged)
Obsolete, given bug 736035

Sign in to add a comment