New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 878334 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: [NTP] Cursor is seen before https:// text and while typing text into it is get vanished.

Reported by db...@etouch.net, Aug 28

Issue description

Chrome Version : 70.0.3534.4 (Official Build) ddfef6cc5ce7547a217eefde728409170be53600-refs/branch-heads/3534@{#11} 32/64 bit
OS : Windows (7, 8, 8.1, 10), Linux(14.04 LTS), Mac Mini (10.13.1, 10.12.6)

Precondition: Enabled 'Enable using the Google local NTP' and 'New Tab Page Custom Links' flag from chrome://flags.

What steps will reproduce the problem?
(1) Launch chrome, open NTP and Click on 'Add Shortcut' button('Edit shortcut' overlay opened). 
(2) Press Tab key upto focus reaches to 'URL', observe cursor position.

Actual: Cursor is seen before https:// text and while typing text into it is get vanished.

Expected: Cursor should seen after https:// and while typing into it htpps:// should get added.

This is a regression issue, broken in 'M70',below is bisect info:

Good Build:70.0.3532.0(Revision: 585633)
Bad Build: 70.0.3533.0 (Revision: 586155)

You are probably looking for a change made after 586011 (known good), but no later than 586057 (first known bad).
CHANGELOG URL:

https://chromium.googlesource.com/chromium/src/+log/3da2da6a07d1df3f9cd3aed22dd3dbdd2d2ca262..765de89597de3bc04859164c038eec9926f7a477

Suspect: r586024 ?

@kristipark: 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.

Note: Unable to provide bisect-per-revision hence providing suspect from Narrow bisect.
 
Actual_Cursor.mov
3.1 MB View Download
Expected_Cursor.mov
1.9 MB View Download
Status: WontFix (was: Assigned)
This is intended behavior. We'll also be removing the "https://" placeholder in a future CL.

Sign in to add a comment