New issue
Advanced search Search tips

Issue 859044 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 849996
Owner:
Closed: Oct 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression: Default cursor is not seen in the passphrase textbox.

Reported by aiman.an...@etouch.net, Jun 29 2018

Issue description

Chrome Version : 69.0.3476.0 (Official Build) 86d261c5d8d1e6cd27cd72f8887c8de670f11b48-refs/branch-heads/3476@{#1} (32/64-bits).

OS: Win (7,8,8.1,10), Mac OS X (10.12.6,10.13.1,10.13.6), Linux (14.04 LTS).

Steps to reproduce:
1. Launch Chrome and 'Sign in to chrome' from 'Avtar icon' with a valid 'Pass-Phrase' enabled account.
2. After successful sign in, Navigate to chrome://settings page, Click on 'Sync' option.
3. Observe the Pass-Phrase text-box.

Actual:  Cursor is not seen in the passphrase textbox.
Expected:  Cursor should be seen in the passphrase textbox.

This is regression issue broken in ‘M-68’ and below is the  has-bisect per-revision info:
Good Build: 68.0.3425.0 (Revision:557063)
Bad Build:  68.0.3427.0  (Revision:557758)

You are probably looking for a change made after 557076 (known good), but no later than 557077 (first known bad).

CHANGE-LOG 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/93e0c457e3eaa198899e7498526c24f1e1260ac0..ba0669a2a785eabe7b86248605579c7a2a66b96d?pretty=fuller&n=10000

Suspecting: https://chromium.googlesource.com/chromium/src/+/ba0669a2a785eabe7b86248605579c7a2a66b96d

hcarmona@:  Could you please help to reassign if your change is not the cause for this change. 

Thank You!

 
Actual_Result.mp4
459 KB View Download
Expected_Result.mp4
574 KB View Download
Project Member

Comment 1 by sheriffbot@chromium.org, Oct 10

Cc: droger@chromium.org msarda@chromium.org bsazonov@chromium.org ew...@chromium.org tangltom@chromium.org sabineb@chromium.org jlebel@chromium.org
--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
Labels: -Pri-1 Pri-3
This is a low priority bug. Marking as such
Mergedinto: 831030
Status: Duplicate (was: Assigned)
Mergedinto: -831030 849996

Sign in to add a comment