New issue
Advanced search Search tips

Issue 855665 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 848030
Owner:
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

URL Bar stays in place when window is dragged

Project Member Reported by nakulj@google.com, Jun 22 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10718.13.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.15 Safari/537.36
Platform: 10718.13.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. open a chrome window
2. click the url bar
3. drag the chrome window somewhere else

What is the expected behavior?
the url bar should cleanly move with the window

What went wrong?
The url bar stays in place.

Did this work before? Yes 

Chrome version: 68.0.3440.15  Channel: n/a
OS Version: 10718.13.0
Flash Version:
 
Components: -UI UI>Browser>Omnibox UI>Shell>WindowManager
Labels: Needs-TestConfirmation
nakulj@, I don't quite understand the steps here.  Are you trying to drag the window from the URL bar (i.e., clicking on it, not releasing the mouse button, then starting the drag?).  Can you provide clearer steps or a video?  thanks!

Comment 4 by nakulj@google.com, Jun 26 2018

http://go/scrcast/NTQwNzExMDI2MzIwOTk4NHxiMTQ5MWUwOC0yOA

Hope that clarifies what I mean :)

Comment 5 by nakulj@google.com, Jun 26 2018

I think the cursor position is a little misleading in the video.
Note that I first click the url bar so that it 'expands'. Then I release the mouse button, move it over the window frame, then drag the frame around. The url bar 'frame' stays in place instead of disappearing.
Owner: tommycli@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for the video.  tommycli@, can you look into this?
Mergedinto: 848030
Status: Duplicate (was: Assigned)
For Beta 68.0.3440.17 and later, this should already be fixed. 

Can you try to update the Chromebook and confirm?

Comment 8 by nakulj@google.com, Jun 26 2018

Updated, looks fixed now. Thanks!

Sign in to add a comment