Issue is also seen for 2 nd User i.e. 
1)Sign into User with User name  more than 9 characters(Ex: Chrome TechM is User Id)
2)Now sign out and click on User id for 'Remove this User' option ->
Now enter wrong password and observe Error message is seen overlapped with 'Remove this User' option

Please refer screenshots

Deleted: Actual_OverlappingOfRemovethisUserOptionAndErrorMessage.jpg 631 KB

	Actual_OverlappingOfRemovethisUserOptionAndErrorMessage.jpg 631 KB View Download

Deleted: Actual_Overlapping OfUserDetails andSubmitButton.jpg 434 KB

	Actual_Overlapping OfUserDetails andSubmitButton.jpg 434 KB View Download

Deleted: Expected.jpg 3.9 MB

	Expected.jpg 3.9 MB View Download

Expected: No Overlapping of 'Submit' button and Owner details and also Error message with 'Remove this User' option should be seen in Sign out screen for User name with 9-14 characters

Actual: Instead Overlapping of 'Submit' button and Owner details is seen and 
also  overlapping of Error message with 'Remove this User' option is seen

Note:
1.Attaching screenshot where UserId Arrow and 'Submit' button is seen in same column(UserName with 10 characters)
2.Adding RB-Stable Blocker as this is a recent Regression. 
Please undo if not the case.
3.Issue is not applicable to Linux and windows

Deleted: Actual.jpg 932 KB

	Actual.jpg 932 KB View Download

This should be intended UI. elizabethchiu@ please confirm or provide a new spec for such cases.

For the overlapping of the submit button, I chatted with Colin to blur the UI that is under the dropdown. We will have a thorough UI implementation review tomorrow to go over these.

elizabethchiu@ this stable blocker issue has not been updated since July 6th. Can you please update and/or close this issue? This doesn't look like a stable blocker at this point.

The overlapping between error message and owner detail menu is already removed. The overlapping between submit button and owner detail menu is acceptable.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-61; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-61 label, otherwise remove Merge-TBD label. Thanks.

The fix landed between branch point.