Correction : 
Unable to reproduce the issue on 68.0.3436.0/10701.0.0 - Kip

>>> Unable to reproduce the issue on 68.0.3437.0/10701.0.0 - Kip

Unable to reproduce the issue on Reks device - 10704.0.0/68.0.3437.0

Deleted: IMG_4277.JPG 1.9 MB

	IMG_4277.JPG 1.9 MB View Download

For comment#3, need to click on the "Remove this User" to get the issue.  Sorry to confuse you.  

Steps to reproduce the issue :
1. create multiple user accounts 
2. select non-owner account on Sign in screen
3. click on down-arrow icon, and click on the "Remove this User"
4. check the "Remove this User" on the info dialog box.

Able to reproduce this issue on 68.0.3437.0/10705.0.0 dev-cahnnel Daisy,Reks and Candy

I ran into this today while attempting to do some testing, I had to switch to the WebUI.

 Issue 846718  has been merged into this issue.

Unable to delete user account on M68-ChromeOS:10718.9.0/68.0.3440.11 

Deleted: 20180601_115011.jpg 1.5 MB

	20180601_115011.jpg 1.5 MB View Download

We're going to disable views login on 68

Issue 851116 has been merged into this issue.

Issue 827416 has been merged into this issue.

 Issue 854569  has been merged into this issue.

69.0.3473.0 (Official Build) dev (64-bit)
10820.0.0 (Official Build) dev-channel eve
Google_Eve.9584.151.0


As a work-around, I thought that I would be able to go into "Settings->Manage Other People", but that reliably crashes Chrome for me. It might or might not be related to the fact that the account that I want to remove from my Chromebook has already been deleted by Google.

Is this related to the same bug, or should I create a separate bug?

dev channel has been pushed with this and users are starting to experience this issue of not being able to delete users.

FWIW: you can still delete a user by switching to webui or by hitting enter twice on the remove user prompt. But a CL fixing this will be landing very soon (today or early next week).

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/03bddaa3e7decc024cd5d878b7db9cf7be4e6887

commit 03bddaa3e7decc024cd5d878b7db9cf7be4e6887
Author: Quan Nguyen <qnnguyen@chromium.org>
Date: Fri Jun 29 23:00:22 2018

Fix bug where Remove User button was not showing after initial click.

Bug:  845657 
Change-Id: I9f7ea848fc469d06cfbbdf91c97260ff95ac9033
Reviewed-on: https://chromium-review.googlesource.com/1112750
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571696}
[modify] https://crrev.com/03bddaa3e7decc024cd5d878b7db9cf7be4e6887/ash/login/ui/login_bubble.cc
[modify] https://crrev.com/03bddaa3e7decc024cd5d878b7db9cf7be4e6887/ash/login/ui/login_bubble.h
[modify] https://crrev.com/03bddaa3e7decc024cd5d878b7db9cf7be4e6887/ash/login/ui/login_bubble_unittest.cc

landed in 10834.0.0 which should be pushed in canary channel tomorrow.

seems like I can't click it because it doesn't fit in the display.

is this a Japanese language string issue or the UI in general issue ? 

I can put in tablet mode and rotate to portrait mode to see the delete user button.

Likely the widget is not being sized large enough; the button should always be present.

the widget is large enough, it's just that it's not possible to scroll, and the bottom end is off the bottom of the screen so the button is not visible

Can we see a screenshot of the issue?

Assuming I have the right idea of what it looks like right now, we could potentially try one of two solutions for the widget going off screen vertically:

1. Shift its position vertically until it just touches the bottom edge of the screen.

2. Resize the widget so its bottom edge just touches the bottom of the screen, and make the widget scrollable.

Not sure which is preferable (or maybe something else). I'm somewhat more in favor of shifting its position so the button is always visible.

I suspect shifting the position will be simpler to implement and also easier to use, since the user would otherwise need to scroll.

Since this tracker is for a slightly different issue, I'm going to close it. A new bug has been opened (crbug/861791) for the widget positioning issue.