starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows notifications gets on silent mode #2585

New Issue
Closed
opened 2026-01-30 22:58:58 +00:00 by claunia · 14 comments
claunia commented 2026-01-30 22:58:58 +00:00
Owner
Copy Link

Originally created by @solispauwels on GitHub (Jul 5, 2019).

Environment

Windows build number:  10.0.18362.175
Windows terminal version: v0.2.1831.0

Steps to reproduce

  • Open windows terminal
  • Click on maximize icon

Expected behavior

Get simply a maximized window

Actual behavior

The maximized windows causes notifications to be in silent mode (without notification) and does not get out of silent mode even passing to another application.

This is possible related to the unable access tothe task bar issue

Originally created by @solispauwels on GitHub (Jul 5, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.175 Windows terminal version: v0.2.1831.0 ``` # Steps to reproduce - Open windows terminal - Click on maximize icon # Expected behavior Get simply a maximized window # Actual behavior The maximized windows causes notifications to be in silent mode (without notification) and does not get out of silent mode even passing to another application. This is possible related to the unable access tothe task bar issue
claunia commented 2026-01-30 22:58:59 +00:00
Author
Owner
Copy Link

@atruskie commented on GitHub (Jul 7, 2019):

So I've noticed this too.

This is an issue with the Focus Assist tool. I believe it is conflating Full Screen with a Maximized window.
image

If you disable focus assist the issue does not happen. However, I like focus assist...

@atruskie commented on GitHub (Jul 7, 2019): So I've noticed this too. This is an issue with the _Focus Assist_ tool. I believe it is conflating _Full Screen_ with a _Maximized_ window. ![image](https://user-images.githubusercontent.com/1452968/60763023-fcf24400-a0ae-11e9-91c1-c7b95191d34d.png) If you disable focus assist the issue does not happen. However, I like focus assist...
claunia commented 2026-01-30 22:58:59 +00:00
Author
Owner
Copy Link

@solispauwels commented on GitHub (Jul 7, 2019):

In any case when you click on maximize the expected behavior is to get a maximized window, not a full screen window

@solispauwels commented on GitHub (Jul 7, 2019): In any case when you click on maximize the expected behavior is to get a maximized window, not a full screen window
claunia commented 2026-01-30 22:58:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 8, 2019):

This will also break autohiding taskbars and some other things. There's ... some magic we need to do here like Chromium and VS where they jiggle the window size by 1px to make things "magically work."

@DHowett-MSFT commented on GitHub (Jul 8, 2019): This will also break autohiding taskbars and some other things. There's ... some magic we need to do here like Chromium and VS where they jiggle the window size by 1px to make things "magically work."
claunia commented 2026-01-30 22:59:00 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 8, 2019):

Link: #1625.

@DHowett-MSFT commented on GitHub (Jul 8, 2019): Link: #1625.
claunia commented 2026-01-30 22:59:00 +00:00
Author
Owner
Copy Link

@ffes commented on GitHub (Oct 2, 2019):

From my experience, when I maximize on my primary screen I don't see the silent mode problem. When I maximize on another than the primary screen I do see this issue.

@ffes commented on GitHub (Oct 2, 2019): From my experience, when I maximize on my primary screen I don't see the silent mode problem. When I maximize on another than the primary screen I do see this issue.
claunia commented 2026-01-30 22:59:00 +00:00
Author
Owner
Copy Link

@ffes commented on GitHub (Nov 14, 2019):

To add to my previous comment... It only happens when you disable the taskbar on secondary screens.

So that means is it full screen on a secondary screen and the switch to silent mode is at least explainable. Maybe there is a check for window size vs screen size (just speculating).

Still not what you want. And terminal is the only application I see this behavior.

@ffes commented on GitHub (Nov 14, 2019): To add to my previous comment... It only happens when you disable the taskbar on secondary screens. So that means is it full screen on a secondary screen and the switch to silent mode is at least explainable. Maybe there is a check for window size vs screen size (just speculating). Still not what you want. And terminal is the only application I see this behavior.
claunia commented 2026-01-30 22:59:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 2, 2020):

This is the same root cause as /dup #1438, so I'm going to merge them together as "the class of issues about windows thinking we're a game and suppressing shell features."

@DHowett-MSFT commented on GitHub (Mar 2, 2020): This is the same root cause as /dup #1438, so I'm going to merge them together as "the class of issues about windows thinking we're a game and suppressing shell features."
claunia commented 2026-01-30 22:59:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 2, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 2, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-30 22:59:02 +00:00
Author
Owner
Copy Link

@ffes commented on GitHub (Mar 17, 2020):

This is was identified and closed as a dup of #1438 which should be fixed in v0.10.761.0, but the case I describe here above in https://github.com/microsoft/terminal/issues/1840#issuecomment-537595876 and https://github.com/microsoft/terminal/issues/1840#issuecomment-553872381 are NOT fixed.

Please reopen this issue!

/cc @DHowett-MSFT

@ffes commented on GitHub (Mar 17, 2020): This is was identified and closed as a dup of #1438 which should be fixed in v0.10.761.0, but the case I describe here above in https://github.com/microsoft/terminal/issues/1840#issuecomment-537595876 and https://github.com/microsoft/terminal/issues/1840#issuecomment-553872381 are **NOT** fixed. Please reopen this issue! /cc @DHowett-MSFT
claunia commented 2026-01-30 22:59:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Thanks!

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Thanks!
claunia commented 2026-01-30 22:59:03 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Since it's a fairly minor p3, and we're past the p3 cutoff for version 1 I'm scoping it out, but if somebody were to help us investigate and fix it I'd definitely take the fix for v1.

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Since it's a fairly minor p3, and we're past the p3 cutoff for version 1 I'm scoping it out, but if somebody were to help us investigate and fix it I'd definitely take the fix for v1.
claunia commented 2026-01-30 22:59:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2021):

Okay so this seems crazy, but this seems like it's fixed on Windows 11. Neither maximizing nor fullscreening seems to trigger Focus Assist mode anymore. However, I just checked with my Windows 10 laptop and that does still hit this when fullscreening.

I'm gonna leave this open, but considering the OS Shell waws able to seemingly fix this on their side, then maybe trying to fix this on our side for Windows 10 might not be the right solution.

MSFT:27639447 looks related, MSFT:33503732 more specifically, oh that one's fixed in 22425.1001.rs_prerelease.210720-1539....

@zadjii-msft commented on GitHub (Dec 9, 2021): Okay so this seems crazy, but this seems like it's fixed on Windows 11. Neither maximizing nor fullscreening seems to trigger Focus Assist mode anymore. However, I just checked with my Windows 10 laptop and that _does_ still hit this when fullscreening. I'm gonna leave this open, but considering the OS Shell waws able to seemingly fix this on their side, then maybe trying to fix this on our side for Windows 10 might not be the right solution. MSFT:27639447 looks related, MSFT:33503732 more specifically, oh that one's fixed in `22425.1001.rs_prerelease.210720-1539`....
claunia commented 2026-01-30 22:59:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2021):

Actually, looking through our internal bug tracker, I did find the fix to the OS. That was in fact MSFT:33503732 which is fixed in 22425.1001.rs_prerelease.210720-1539. The details in that bug also seem to suggest that it's definitely an OS bug, and not something that applies uniquely to the Terminal. I'm gonna mark this as a dupe of that resolved bug. The fix should be out soontm

/dup https://task.ms/33503732

@zadjii-msft commented on GitHub (Dec 9, 2021): Actually, looking through our internal bug tracker, I did find the fix to the OS. That was in fact MSFT:33503732 which is fixed in `22425.1001.rs_prerelease.210720-1539`. The details in that bug also seem to suggest that it's definitely an OS bug, and not something that applies uniquely to the Terminal. I'm gonna mark this as a dupe of that resolved bug. The fix should be out soon<sup>tm</sup> /dup https://task.ms/33503732
claunia commented 2026-01-30 22:59:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 9, 2021):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Dec 9, 2021): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Help Wanted Issue-Bug Priority-3 Product-Terminal Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2585
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?