New issue
Advanced search Search tips

Issue 867301 link

Starred by 1 user
Status: Duplicate
Merged: issue 853439
Owner: ----
Closed: Jul 25
Cc:
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Autocomplete in CSS rules tab requires two hits of the enter button

Reported by bran...@promotionsonly.com.au, Jul 25 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Add a new CSS rule to any object
2. Type the following and hit enter: 'disp'
3. Type the following and hit enter: 'blo'
4. Type the following and hit enter: 'display'
5. Type the following and hit enter: 'block'

You have to hit enter/return twice when you actually type the full property yourself (aka not using the autocompletion I think?)

What is the expected behavior?
You usually have to press enter once.

What went wrong?
You have to press enter twice.

Did this work before? Yes 67

Chrome version: 68.0.3440.75  Channel: stable
OS Version: 10.0
Flash Version:

Comment 1 by vamshi.kommuri@chromium.org, Jul 25

Labels: Needs-Triage-M68 Needs-Bisect

Comment 2 by bran...@promotionsonly.com.au, Jul 25 

Having some trouble creating a repro but I think it occurs to properties with multiple matched values in the auto completion, e.g display: block matches inline-block and block etc.

Comment 3 by bran...@promotionsonly.com.au, Jul 25 

I think this is relating to the 'better autocompletion' update that was added to console in 68.

Comment 4 by susan.boorgula@chromium.org, Jul 25

Cc: susan.boorgula@chromium.org
Labels: -Needs-Bisect Triaged-ET
Mergedinto: 853439
Status: Duplicate (was: Unconfirmed)
brandon@ Thanks for the issue.

This issue looks to be similar to issue 853439, hence duping this issue to 853439 and removing 'Needs-Bisect' label.

Note: Able to reproduce the issue on Windows 10 and Mac OS 10.13.3 on the latest Stable 68.0.3440.75 and the issue is fixed on the latest Canary 70.0.3501.2.
Unable to reproduce the issue on Ubuntu 14.04.

Thanks..
►

Sign in to add a comment