Open jrovny opened 3 years ago
Setting false
for either IsTabStop
or IsEnabled
for contents of the parent page (that spawns the content dialog) does not respond to values of false
. ContentDialog
does not effectively prevent interaction until it is handled, allowing user to tab
through controls at will.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Commenting on this to prevent it from going stale. I just tested this and it's still an issue.
Describe the bug When a content dialog is opened and the main window below has controls with access keys, I'm able to hotkey to the window below the content dialog. My understanding, per this link, is that the content dialog should prevent the user from being able to hotkey and focus to controls outside the dialog.
Steps to reproduce the bug In the example below, when the content dialog is open and the initial focus is on the textbox with the header of "UD," I'm able to click Alt+U and switch focus to the window below the dialog. I can then continue interacting with the controls on the window below the dialog, such as typing the word "Test" as I did in the image.
Expected behavior Dialog should prevent focusing or hot-keying to the app window below the dialog.
Screenshot
Version Info NuGet package version: [Microsoft.ProjectReunion.WinUI 0.8.2]. Namespace: Microsoft.UI.Xaml.Controls for the ContentDialog control. WinUI3 for Win32. Windows version May 2020 Update (19041). Desktop.