When on a full-screen chrome window, if user accidentally detaches tab, it is immediately transferred to another window, even without letting go of tab. |
||||
Issue descriptionChrome Version : 69.0.3497.92 (Official Build) (64-bit) URLs (if applicable) : OS version : 10.13.6 Behavior in Safari (if applicable): Tab remains floating until user stops holding it; it can be placed back on window. Behavior in Firefox (if applicable): What steps will reproduce the problem? (1) Open new Chrome instance (2) Make it full screen (green button, so that it has its own window) (3) Add one or more tabs (4) Detach any tab from browser, without letting go of it (keep 'holding' it) (5) Attempt to place tab back into the Chrome window it was initially in What is the expected result? User should be able to 'hold' detached tab within the same window without the tab immediately going into its own window. This used to be the result before the latest UI update. What happens instead? Detached tab immediately goes to new window, and it's annoying/time consuming to try to put the tab back where it was. This happens a lot when I'm trying to reorganize tabs and accidentally detach a tab. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. Graphics Feature Status Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Hardware accelerated Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Unavailable Rasterization: Hardware accelerated Skia Deferred Display List: Disabled Skia Renderer: Disabled Surface Synchronization: Enabled Video Decode: Hardware accelerated Viz Service Display Compositor: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated Driver Bug Workarounds
,
Sep 18
Probably related to issue 883910.
,
Sep 18
,
Sep 25
,
Nov 20
***Mass UI Triage *** Able to reproduce the issue on Mac with chrome #72.0.3615.0 |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Sep 18