Windows version
Windows 11
Windows OS build
24H2 (OS Build 26100.7462)
YASB version installed
1.9.1 x64 (Stable)
Describe the bug
Hi, thank you first of all for developing this wonderful piece of software.
Lately I have experienced some odd behavior when having YASB active and using Firefox taskbar tabs (the native Firefox PWA "apps", which have been implemented in the browser not too long ago).
What happens is the following:
- Upon launch, if the pinned Firefox taskbar tabs are clicked on from the taskbar before YASB is initiated, the tabs in question will open as normal from their respective icon, separate from the main Firefox taskbar icon. This is the intended behavior.
- Instead, if those taskbar tabs are started after launching YASB, the tabs will open from the main Firefox taskbar icon instead of their own taskbar icon, as if they were a normal Firefox instance.
This only happens while using YASB. Closing Firefox, quitting YASB, then re-opening Firefox and its taskbar tabs without YASB running consistently restores the intended behavior.
Widgets currently active:
- "clock",
- "launchpad"
- "systray",
- "cpu",
- "memory",
- "disk",
- "traffic",
- "volume",
- "settings",
- "notifications",
- "power_menu"
[I am also including here an excerpt from the log, but I'm not noticing anything special that might be relevant to this issue].
Relevant log output
2026-04-01 11:01:37,947 [INFO] [MainThread] [root/log.py:99]: YASB v1.9.1
2026-04-01 11:01:37,948 [INFO] [CLIPipeServer] [cli_server/cli_server.py:215]: CLI server started v1.1.6
2026-04-01 11:01:37,949 [INFO] [MainThread] [cli_server/cli_server.py:106]: Log pipe server started
2026-04-01 11:01:39,186 [INFO] [MainThread] [root/service.py:52]: AudioOutputService starting...
2026-04-01 11:01:39,356 [INFO] [MainThread] [root/bar_manager.py:95]: Starting WindowsNotificationEventListener...
2026-04-01 11:01:39,358 [INFO] [MainThread] [root/watcher.py:65]: Watching directory: c:\users\[username]\.config\yasb
2026-04-01 11:01:39,358 [INFO] [MainThread] [root/watcher.py:104]: Created file watcher
2026-04-01 11:01:39,702 [INFO] [MainThread] [root/update_service.py:429]: Background update checker started
2026-04-01 11:01:40,055 [DEBUG] [MainThread] [systray_widget/systray.py:614]: Loading state from C:\Users\[username]\AppData\Local\YASB\systray_state_[xxx].json
2026-04-01 11:01:40,064 [DEBUG] [SystrayMonitor] [systray_widget/systray.py:63]: Systray monitor thread is starting...
2026-04-01 11:01:40,273 [DEBUG] [SystrayMonitor] [systray_widget/systray_monitor.py:119]: Adding TaskbandHWND prop to hwnd 67164
2026-04-01 11:01:40,274 [DEBUG] [SystrayMonitor] [systray_widget/systray_monitor.py:197]: Finding real tray hwnd
2026-04-01 11:01:40,283 [DEBUG] [MainThread] [systray_widget/systray.py:261]: Sending TaskbarCreated message: 49337
2026-04-01 11:01:40,283 [DEBUG] [MainThread] [systray_widget/systray.py:263]: Systray icons refreshed
Windows version
Windows 11
Windows OS build
24H2 (OS Build 26100.7462)
YASB version installed
1.9.1 x64 (Stable)
Describe the bug
Hi, thank you first of all for developing this wonderful piece of software.
Lately I have experienced some odd behavior when having YASB active and using Firefox taskbar tabs (the native Firefox PWA "apps", which have been implemented in the browser not too long ago).
What happens is the following:
This only happens while using YASB. Closing Firefox, quitting YASB, then re-opening Firefox and its taskbar tabs without YASB running consistently restores the intended behavior.
Widgets currently active:
[I am also including here an excerpt from the log, but I'm not noticing anything special that might be relevant to this issue].
Relevant log output