New issue
Advanced search Search tips

Issue 626953 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

Tab dragged out of maximised window to edge of screen does not snap to half screen

Reported by mland...@gmail.com, Jul 10 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1.In Windows 10, Maximise a Chrome window containing several tabs.
2. Drag one of the tabs out of the window, taking the mouse to the side edge of the screen with the left button still depressed.

What is the expected behavior?
The new window Chrome creates for the tab should snap to half the screen using Windows 10 snap.

What went wrong?
Windows shows the outline indicating a half-screen snapped window is to be produced, but then loses this even while the mouse is held with left-button still depressed at the edge of the screen. When the mouse button is released, the new window for the tab is created Maximised instead of snapped to half the screen.

Did this work before? No 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

I don't believe this ever worked in Windows 10.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 11 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by mland...@gmail.com, Jul 24 2017

This bug remains unchanged. It only affects tabs dragged out of a *maximised* window. Windows 10 Snap works perfectly in all other cases. It is easy to replicate. There must be a simple cause.

Comment 3 by mland...@gmail.com, Jul 24 2017

Could this issue be reopened please?

Sign in to add a comment