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

Issue 898833 link

Starred by 1 user
Status: Duplicate
Merged: issue 798219
Owner: ----
Closed: Oct 26
Cc:
vamshi.kommuri@chromium.org
█ ramyan@chromium.org
treib@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Typing text in search filed bellow doodle moves to upper search bar

Reported by rihaskh@gmail.com, Oct 25 
UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36

Steps to reproduce the problem:
1. click on new tab
2. Enter text to search field bellow doodle 
3. now the entering text moves to upper search field 

What is the expected behavior?
it should stay in the text field bellow the doodle .

What went wrong?
when start to type in text field bellow the doodle its moves to upper search field 

Did this work before? No 

Chrome version: 70.0.3538.67  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
issue in search box.mp4
1.4 MB View Download

Comment 1 by woxxom@gmail.com, Oct 25 

Duplicate of  bug 798219 .

Comment 2 by phanindra.mandapaka@chromium.org, Oct 25

Labels: Needs-Triage-M70

Comment 3 by vamshi.kommuri@chromium.org, Oct 26

Cc: treib@chromium.org vamshi.kommuri@chromium.org
Components: -UI UI>Browser>NewTabPage
Labels: Triaged-ET Target-72 M-72 FoundIn-71 FoundIn-70 FoundIn-72 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Thanks for filing the issue!

Able to reproduce the issue on chrome version 70.0.3538.67  and on the latest canary 72.0.3590.0 using Ubuntu 14.04, Windows 10 and Mac 10.13.1

As the issue is seen from M60(60.0.3112.0) considering it as Non-Regression and marking it as Untriaged.
From  bug 798219  CC'ing 	treib@ for further inputs.

Comment 4 by treib@chromium.org, Oct 26

Cc: ramyan@chromium.org
Mergedinto: 798219
Status: Duplicate (was: Untriaged)
Yup, this is  bug 798219 . As mentioned there, this behavior is by design, even if it's somewhat confusing.
►

Sign in to add a comment