Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TabView TearOutTabs: The TabTearOutWindowRequested event is raised too often #10154

Open
DHancock opened this issue Nov 12, 2024 · 0 comments
Open
Labels
bug Something isn't working needs-triage Issue needs to be triaged by the area owners

Comments

@DHancock
Copy link

Describe the bug

The TabTearOutWindowRequested event is raised every time a tab header is left clicked, right clicked and even when the tab close button is right clicked.

As a result I've had to add code in the repro app below that limits the number of new windows created in the TabTearOutWindowRequested event handler.

If a tab isn't subsequently then torn out, the new window won't be used and remains hidden. To that end I've also had to add code to close it, allowing the app to shutdown.

Repro project: TearOutTabs.zip

Steps to reproduce the bug

.

Expected behavior

I think that the TabTearOutWindowRequested event should only be raised once per tear out sequence, with the new window cached by the tear out code until it's used. Or may be even only raised immediately before a tab is torn out when the tear out process starts.

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.6.1: 1.6.240923002

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response

@DHancock DHancock added the bug Something isn't working label Nov 12, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Issue needs to be triaged by the area owners
Projects
None yet
Development

No branches or pull requests

1 participant