Regression: Dragging a tab into its own window in fullscreen switches immediately to another OS X space |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome in fullscreen with a couple of tabs 2. Open another Chrome window in fullscreen and arrange in a split screen configuration with the window opened in 1, such that windows 1 and 2 are arranged side-by-side 3. Try dragging a tab from window 1 to window 2 What is the expected behavior? Expect to be able to drag the tab between windows. Chrome always used to work this way What went wrong? As soon as the tab is dragged off the existing window, the UI switches to a new OS X Space - i.e. there's only the option to drag the tab into a new, fullscreen window in it's own space. You can drag between existing windows Did this work before? N/A Chrome version: 69.0.3497.81 Channel: n/a OS Version: OS X 10.13.6 Flash Version:
,
Sep 13
Another consequence of this bug, which I just ran into: 1. Drag to reorder a tab within a set of tabs 2. Accidentally drag a little too far, such that the tab is slightly outside its parent window 3. Observe: Tab opens in a new window, fullscreened in a new space. There's no way to correct the accidental drag by dragging back into the parent window. Now I must close the new window and go back to the original window and reopen the URL there - since there's no way to drag a window from one space to another. Very frustrating!
,
Sep 14
,
Sep 14
Thanks for the report. I can reproduce it in Canary. +blocking-label to our related MacViews Fullscreen Master bug.
,
Sep 18
,
Sep 26
,
Oct 2
Any update on this regression?
,
Oct 29
Another issue for you MacViews fullscreen master bug: https://bugs.chromium.org/p/chromium/issues/detail?id=883870#c1
,
Nov 13
Issue 889513 has been merged into this issue.
,
Nov 20
***Mass UI Triage*** We were able to reproduce this bug on latest canary#72.0.3616.0 and it is a Non-Regression issue since seeing this from M60 #60.0.3072.0. Note: Its a mac specific issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mdarby@google.com
, Sep 13