TabControl and DataGrid Issues

[ZhuoWang-NXNX]

Bug explanation

Once I encountered a bug. There was a three-level tab control on a page, and within the third level tab control, there was a datagrid. After I tried to resize the window once, the entire datagrid within the third level tab control crashed directly. Clicking on any control within this area with the mouse had no effect.

Version

5.3.1

[nicolaihenriksen]

@ZhuoWang-NXNX What exactly do you mean by "crashed directly"? I assume your application did not crash, since you mention that you could still (attempt to) click around in the app.

There is currently a known issue, which is being addressed in #4065 where the whole TabControl can become non-interactive (i.e. TabControl.IsHitTestVisible becomes False). Perhaps this is the issue you're experiencing?

[ZhuoWang-NXNX]

The crash might be a translation issue. What I mean is that the content within the third-level tab will not respond when clicked. My situation is that there is a DataGrid within the third-level TabView. After zooming in or out, clicking will no longer work.But I can make the border larger by dragging it with the mouse again.I have moved my original content to the second-level tab now. Everything is working fine.

…

________________________________ 发件人: Nicolai Henriksen ***@***.***> 发送时间: 2026年6月8日 16:48 收件人: MaterialDesignInXAML/MaterialDesignInXamlToolkit ***@***.***> 抄送: ZhuoWang ***@***.***>; Mention ***@***.***> 主题: Re: [MaterialDesignInXAML/MaterialDesignInXamlToolkit] TabControl and DataGrid Issues (Issue #4068) [https://avatars.githubusercontent.com/u/19572699?s=20&v=4]nicolaihenriksen left a comment (MaterialDesignInXAML/MaterialDesignInXamlToolkit#4068)<#4068 (comment)> @ZhuoWang-NXNX<https://github.com/ZhuoWang-NXNX> What exactly do you mean by "crashed directly"? I assume your application did not crash, since you mention that you could still (attempt to) click around in the app. There is currently a known issue, which is being addressed in #4065<#4065> where the whole TabControl can become non-interactive (i.e. TabControl.IsHitTestVisible becomes False). Perhaps this is the issue you're experiencing? ― Reply to this email directly, view it on GitHub<#4068?email_source=notifications&email_token=BKO7HYX42IHZFYS25JSZWND46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4646906446>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKO7HYUCYRYJSGN5N2HEUH346Z4UTAVCNFSM6AAAAACZ6MCUFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNBWHEYDMNBUGY>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/BKO7HYROUV5VGUHK35FJY2D46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/BKO7HYRBLD7ZMQ7JRKAITWL46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[ZhuoWang-NXNX]

The inability to respond means something like the UI getting stuck. However, the content in other areas can still be clicked normally. The issue is that the content within this three-level Tab of the DataGrid is unresponsive.

…

________________________________ 发件人: Wang Zhuo ***@***.***> 发送时间: 2026年6月8日 16:52 收件人: MaterialDesignInXAML/MaterialDesignInXamlToolkit ***@***.***> 主题: 回复: [MaterialDesignInXAML/MaterialDesignInXamlToolkit] TabControl and DataGrid Issues (Issue #4068) The crash might be a translation issue. What I mean is that the content within the third-level tab will not respond when clicked. My situation is that there is a DataGrid within the third-level TabView. After zooming in or out, clicking will no longer work.But I can make the border larger by dragging it with the mouse again.I have moved my original content to the second-level tab now. Everything is working fine.

________________________________ 发件人: Nicolai Henriksen ***@***.***> 发送时间: 2026年6月8日 16:48 收件人: MaterialDesignInXAML/MaterialDesignInXamlToolkit ***@***.***> 抄送: ZhuoWang ***@***.***>; Mention ***@***.***> 主题: Re: [MaterialDesignInXAML/MaterialDesignInXamlToolkit] TabControl and DataGrid Issues (Issue #4068) [https://avatars.githubusercontent.com/u/19572699?s=20&v=4]nicolaihenriksen left a comment (MaterialDesignInXAML/MaterialDesignInXamlToolkit#4068)<#4068 (comment)> @ZhuoWang-NXNX<https://github.com/ZhuoWang-NXNX> What exactly do you mean by "crashed directly"? I assume your application did not crash, since you mention that you could still (attempt to) click around in the app. There is currently a known issue, which is being addressed in #4065<#4065> where the whole TabControl can become non-interactive (i.e. TabControl.IsHitTestVisible becomes False). Perhaps this is the issue you're experiencing? ― Reply to this email directly, view it on GitHub<#4068?email_source=notifications&email_token=BKO7HYX42IHZFYS25JSZWND46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4646906446>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKO7HYUCYRYJSGN5N2HEUH346Z4UTAVCNFSM6AAAAACZ6MCUFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNBWHEYDMNBUGY>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/BKO7HYROUV5VGUHK35FJY2D46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/BKO7HYRBLD7ZMQ7JRKAITWL46Z4UTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRUGY4TANRUGQ3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[nicolaihenriksen]

@ZhuoWang-NXNX Thank you. You wouldn't happen to have a small sample application that can reproduce the issue you can share? Then I can verify if the PR mentioned above will fix it or not. You can also try updating to version 5.3.2, although I don't suspect that will make much of a difference (but you never know for sure).