New issue
Advanced search Search tips

Issue 911510 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Separator line of 'Enter Passphrase' is thicker than Separator line 'Open guest window'.

Project Member Reported by shru...@virtusa.com, Dec 4

Issue description

Chrome Version:73.0.3630.0 (Official Build) 4e0c28599deef67a295ba4ecd2e0180a4b5157e0-refs/branch-heads/3630@{#1}(32/64 bit)

OS: Windows(7,8,8.1,10) , Mac(10.13.1 , 10.13.6 , 10.14.2) and Linux(14.04 LTS)OS 

Pre-condition: Sign in to chrome which has a passphrase for signing.

Steps to reproduce:
1. Launch Chrome and Sign in chrome.
2. 'Error' will be shown in RHS of Omni-box, click on it.
3. Observe the difference between separator line of 'Enter Passphrase' and 'Open guest window'.


Actual Result: Separator line of 'Enter Passphrase' is thicker than Separator line of 'Open guest window'.
Expected Result: Both of the separator lines of 'Enter Passphrase' and 'Open guest window' should be of the same  thickness

Bisect info:
You are probably looking for a change made after 612169 (known good), but no later than 612170 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/34c52daf88e484232cc4d458b7a98255112c6c52..cc13e7ebdd1c65894fc16f3bdacdf36aef19d9f9

Suspect: https://chromium.googlesource.com/chromium/src/+/cc13e7ebdd1c65894fc16f3bdacdf36aef19d9f9

@David Roger: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.	

Thank You!

Kindly refer the attached screencast.
Thank You!
 
 	
 
Actual_result.mov
11.0 MB View Download
Expected_result.mov
10.9 MB View Download
Updates:
This is a regression issue broken in M-72 :

Good build :72.0.3625.0
Bad build  :72.0.3626.0

Thank you 
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 18

--Chrome Identity automated triaging--

This bug is P0 or P1 and has gone two weeks without any activity. Please provide a status update or lower the priority. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Comment 3 by sheriffbot@chromium.org, Jan 2

--Chrome Identity automated triaging--

This bug is P0 or P1 and has gone two weeks without any activity. Please provide a status update or lower the priority. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Comment 4 by sheriffbot@chromium.org, Jan 17 (5 days ago)

--Chrome Identity automated triaging--

This bug is P0 or P1 and has gone two weeks without any activity. Please provide a status update or lower the priority. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Sign in to add a comment