New issue
Advanced search Search tips

Issue 860130 link

Starred by 2 users

Issue metadata

Status: Closed
Owner: ----
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Cannot remove user on the login screen because "Remove this user" clickable is hidden

Project Member Reported by jcliang@chromium.org, Jul 4

Issue description

Chrome Version: 69.0.3464.0
OS: Chrome OS 10799.0.0 soraka

What steps will reproduce the problem?
(1) try to remove a secondary user on the login screen
(2) cannot remove the user because "Remove this user" clickable is hidden
(3)

What is the expected result?

The "Remove this user" clickable should be there.

What happens instead?

The clickable is hidden.


If I keep the remove user dialog and rotate the screen, the "Remove this user" clickable is shown after the screen rotates.

Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
I also happened to see this issue with some of my test accounts while developing other features.

The first button "Remove this user" is visible and clickable. However the second button which appear after it (beneath ASH_LOGIN_POD_NON_OWNER_USER_REMOVE_WARNING_*) messages is invisible and not clicable. See the screenshot.

So far I could see it only with some accounts that has a long email address, so that it's truncated by ellipsis in the view.
As a workaround, if you choose the same menu by keyboard, the cursor stays onto the 2nd button after activating the 1st button. So just hitting [enter] key would allow you to remove a user.
no_button.png
22.4 KB View Download
Status: Closed (was: Untriaged)
<triage> Cannot reproduce on 72.0.3593.0, please reopen if seen again. </triage>

Sign in to add a comment