Bug: Regression: Google Chrome 149 can no longer join existing tabbed containers in Forge (Chromium works correctly)

Aperta
#535 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
javascript, linux
Ambito
desktop

Direzione di ricerca

Reproduce on GNOME 46 with Forge v89 and Google Chrome 149: drag a Chrome window onto an existing tabbed container and confirm the drop is ignored while Chromium works. The payload names no source files, so start by comparing Chrome's and Chromium's window properties (WM_CLASS, window type) against how Forge decides which windows can join a container. Done when Chrome joins an existing tabbed container like Chromium does.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Issue/Bug Description/Video Capture/Screenshots
Environment
  • OS: Ubuntu 24.04.4 LTS
  • Desktop: GNOME
  • Window Manager: Mutter
  • Extension: Forge v89
  • Session: Tested on both X11 and Wayland
  • Google Chrome: 149.0.7827.196
  • Chromium: Current Ubuntu package
Description

After updating Google Chrome to version 149.0.7827.196, Chrome can no longer be attached to an existing tabbed container created by Forge.

The issue started immediately after the Chrome update.

No changes were made to Forge or GNOME configuration.

Expected Behaviour

Dragging a Chrome window onto an existing tabbed container should add it as another tab.

Example:

Terminal
Files
Chrome

Actual Behaviour

Chrome tiles normally and is fully managed by Forge, but it cannot be attached to an existing tabbed container.

The drop operation is ignored.

Important Observation

This affects only Google Chrome.

The following applications can be added to the same tabbed container without any issues:

  • Terminal
  • Files
  • Text Editor
  • WhatsApp Desktop
  • Chromium

Chromium behaves correctly.

Only Google Chrome fails.

What I Tested
  • Fresh Chrome profile

  • Disabled all Chrome extensions

  • X11 session

  • Wayland session

  • Started Chrome with:

    google-chrome --ozone-platform=x11

  • Started Chrome with a temporary user profile

  • Verified WM_CLASS

  • Verified _NET_WM_WINDOW_TYPE_NORMAL

  • Verified Forge itself is working correctly

None of these changed the behaviour.

xprop

Chrome reports:

WM_CLASS = "google-chrome", "Google-chrome"

_NET_WM_WINDOW_TYPE_NORMAL

The window is tiled correctly by Forge.

Conclusion

The problem appears to be a regression introduced in Google Chrome 149.

Forge continues to work correctly with Chromium and other applications.

Please let me know if additional debugging or logging would be useful.

Steps to reproduce

No response

Distribution and Linux version
PRETTY_NAME="Ubuntu 24.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.4 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
Linux swaminathan-14Z980-G-AH52A2 6.17.0-35-generic #35~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 19:30:42 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Journal Logs from the last hour
Jul 04 15:34:59 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19789986) is greater than comparison timestamp (19789956).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:35:01 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19791491) is greater than comparison timestamp (19791486).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:35:09 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19799920) is greater than comparison timestamp (19799916).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:36:08 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19859008) is greater than comparison timestamp (19859006).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:13 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19924082) is greater than comparison timestamp (19924079).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:14 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19924200) is greater than comparison timestamp (19924199).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:35 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19945786) is greater than comparison timestamp (19945785).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:40 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19950380) is greater than comparison timestamp (19950375).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:44 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19954248) is greater than comparison timestamp (19954246).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:37:45 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19955343) is greater than comparison timestamp (19955340).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:38:03 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19973976) is greater than comparison timestamp (19973972).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:38:08 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19978716) is greater than comparison timestamp (19978712).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:38:09 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19979781) is greater than comparison timestamp (19979777).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:38:09 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (19980034) is greater than comparison timestamp (19980032).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:39:19 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (20049351) is greater than comparison timestamp (20049350).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:39:20 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (20050462) is greater than comparison timestamp (20050460).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:39:24 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (20054649) is greater than comparison timestamp (20054646).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:39:25 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (20055745) is greater than comparison timestamp (20055741).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Jul 04 15:39:27 swaminathan-14Z980-G-AH52A2 gnome-shell[3681]: Window manager warning: last_focus_time (20058054) is greater than comparison timestamp (20058051).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
GNOME Shell version

GNOME Shell 46.0

Forge version

[email protected] Name: Forge Description: Tiling and window manager for GNOME - Please report bugs/issues on https://github.com/forge-ext/forge/issues - Needs a new maintainer. Path: /home/swaminathan/.local/share/gnome-shell/extensions/[email protected] URL: https://github.com/forge-ext/forge Version: 89 Enabled: Yes State: ACTIVE

Other installed/enabled extensions
[email protected]
  Name: Forge
  Description: Tiling and window manager for GNOME
- Please report bugs/issues on https://github.com/forge-ext/forge/issues
- Needs a new maintainer.
  Path: /home/swaminathan/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/forge-ext/forge
  Version: 89
  Enabled: Yes
  State: ACTIVE

[email protected]
  Name: AppIndicator and KStatusNotifierItem Support
  Description: Adds AppIndicator, KStatusNotifierItem and legacy Tray icons support to the Shell
  Path: /home/swaminathan/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/ubuntu/gnome-shell-extension-appindicator
  Version: 64
  Enabled: Yes
  State: ERROR

[email protected]
  Name: GSConnect
  Description: GSConnect is a complete implementation of KDE Connect especially for GNOME Shell with Nautilus, Chrome and 
Firefox integration. It does not rely on the KDE Connect desktop application and will not work with it installed.

KDE Connect allows devices to securely share content like notifications or files and other features like SMS messaging and
 remote control. The KDE Connect team has applications for Linux, BSD, Android, Sailfish, iOS, macOS and Windows.

Please report issues on Github!
  Path: /home/swaminathan/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/GSConnect/gnome-shell-extension-gsconnect/wiki
  Version: 72
  Enabled: Yes
  State: ACTIVE

[email protected]
  Name: Auto Move Windows
  Description: Move applications to specific workspaces when they create windows.
  Path: /usr/share/gnome-shell/extensions/[email protected]
  URL: https://gitlab.gnome.org/GNOME/gnome-shell-extensions
  Enabled: Yes
  State: ACTIVE

[email protected]
  Name: Desktop Icons NG (DING)
  Description: Adds icons to the desktop. Fork of the original Desktop Icons extension, with several enhancements .
  Path: /usr/share/gnome-shell/extensions/[email protected]
  URL: https://gitlab.com/rastersoft/desktop-icons-ng
  Enabled: Yes
  State: ACTIVE

[email protected]
  Name: Ubuntu AppIndicators
  Description: Support app indicators and legacy tray icons in top panel, as the default Ubuntu experience. System update 
of AppIndicator and KStatusNotifierItem Support extension.
  Path: /usr/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/ubuntu/gnome-shell-extension-appindicator
  Enabled: Yes
  State: ACTIVE

[email protected]
  Name: Ubuntu Dock
  Description: A dock for the Gnome Shell, default Ubuntu experience. This extension is a modified version of Dash To Dock
 with different defaults. Dash To Dock can be installed to replace it and give more (but unsupported) configuration option
s.
  Path: /usr/share/gnome-shell/extensions/[email protected]
  URL: https://micheleg.github.io/dash-to-dock/
  Original author: [email protected]
  Version: 90
  Enabled: Yes
  State: ACTIVE
Monitor Setup

Single Monitor

Monitor: LG 32-inch (connected via HDMI)
Resolution: 2560 × 1440 (QHD)
Refresh Rate: 59.91 Hz
Scaling: 100%
Orientation: Landscape
Primary Display: Yes

Single external monitor

  • LG 32-inch monitor
  • Connected via HDMI (HDMI-1)
  • Primary display
  • Resolution: 2560 × 1440 (QHD)
  • Refresh rate: 59.91 Hz
  • Scaling: 100%
  • Landscape orientation

xrandr:
HDMI-1 connected primary 2560x1440+0+0

Other Notes

would also add this comparison table

Application | Tiles | Can Join Tab Group -- | -- | -- Terminal | Yes | Yes Files | Yes | Yes Text Editor | Yes | Yes WhatsApp Desktop | Yes | Yes Chromium | Yes | Yes Google Chrome 149 | Yes | No

That table immediately tells the maintainer where to look.

Lingua principale
JavaScript
Stelle
1.3k
Fork
112
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di forge-ext/forge

Tutte le issue di forge-ext/forge

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.