moving tabs to a new window no longer works.

Bug #1918269 reported by rew
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Somewhat similar to bug #999632, but different and quite new.

When I have a tab that I want to move to a NEW window, I used to be able to drag the tab and then when releasing it near the tab bar of another chromium window, it would snap into that window's tab list. This still works.

But when I release the tab NOT near the tab bar of another window, it used to create a new window. This is convenient: I have multiple screens so when I decide I need to view this tab alongside something in my existing window, I drag the tab to create a new window on the other screen.

Workaround: create a new window first then drag the tab there. But this "used to work". It is not necessary to do it like this. I liked it the old way.

This changed somewhere in the last week. The behaviour swapped on my home computer yesterday (but it was still normal at work) and today I had to restart chromium (because all new tabs were reporting "aw snap!", reported in another bugreport) and now it's here too. Package: chromium
Versions:

Reverse Depends:
  chromium-bsu,chromium 0.9.14
  x2gothinclient-minidesktop,chromium
  webext-ublock-origin,chromium
  webext-proxy-switcher,chromium
  webext-privacy-badger,chromium
  webext-bulk-media-downloader,chromium
  webext-browserpass,chromium
  polymake,chromium
  gnome-core,chromium
  djview-plugin,chromium
  cinnamon-desktop-environment,chromium
  chromium-tt-rss-notifier,chromium
  chromium-lwn4chrome,chromium
  chromium-bsu,chromium 0.9.14
  chrome-gnome-shell,chromium
  chrome-gnome-shell,chromium
Dependencies:
Provides:
Reverse Provides:

Description: Ubuntu 20.04.2 LTS
Release: 20.04

% apt-cache policy chromium
chromium:
  Installed: (none)
  Candidate: (none)
  Version table:
% []

Revision history for this message
Olivier Tilloy (osomon) wrote :

What version of chromium are you running? (please share the output of "chromium --version")

I suspect this might be a regression in the 89.0.4389.72 stable update, that was subsequently fixed in 89.0.4389.82, and is now available in the stable channel of the snap store.

If your version is 89.0.4389.72, please close all chromium windows, upgrade to 89.0.4389.82 (run "sudo snap refresh") and let us know whether the latest update helps. Thanks!

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
rew (r-e-wolff) wrote :

% chromium --version
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 89.0.4389.82 snap
%

Revision history for this message
rew (r-e-wolff) wrote :

Nope.... Not fixed.... But I think the behaviour changed from last time I tested it (my machine crashed inbetween... Grrr..).

So now, when I drag a tab it shows as a new window, and stays "attached to the mouse" until it snaps into an existing window when I come close to the tab bar in the other window.

Then.... on the next click anywhere on any of my screens, the tab that was just parked as a tab in a window is suddenly detached and placed randomly.... (i.e. as far as I can see: Not where I released the drag nor where I clicked).

Revision history for this message
rew (r-e-wolff) wrote :

Just verfied on my other machine: Same chrome version (Chromium 89.0.4389.82 snap) but slightly different behaviour.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
Revision history for this message
rew (r-e-wolff) wrote :

I switched to chrome.
Chrome started to have the same behavior, while IIRC, above I reported it didn't.

Changed in chromium-browser (Ubuntu):
status: Expired → New
Revision history for this message
Olivier Tilloy (osomon) wrote :

So that's an upstream change, not specific to the chromium snap. Can you please file a bug at https://crbug.com/ and share the link here?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.