You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dialog content is cut off when performing the described reproduction steps.
Bug:
You must have DPI 125%, 150% and 175% and Windows 10
You must enable the vertical scrollviewer of the dialog content.
Remove the Title and/or Buttons from the dialog, the problem is more evident.
Add a quantity of text that shows the scrollviewer
If the last line has letters like g, j - the end may be cut off when scrolling with the mouse.
Investigating, we realized that Microsoft's own Content dialog ends up making the wrong calculation when enabling the vertical scrollviewer.
This problem occurs specifically in UWP, Windows 10.
Through investigation, it was discovered that when using fixed values
The component behaves properly, but this approach is problematic because it does not know the fixed size of the content.
The correct way is to use it the way Microsoft itself uses it:
Steps to reproduce the bug
Bug:
Must have DPI 125%, 150% and 175% and Windows 10
Must enable the vertical scrollviewer of the Dialog content.
Remove the Title and/or Buttons from the dialog, the problem is more evident.
Add a quantity of text that shows the scrollviewer
If the last line has letters like g, j - the end may be cut off when scrolling with the mouse.
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.2
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
The dialog content is cut off when performing the described reproduction steps.
Bug:
Investigating, we realized that Microsoft's own Content dialog ends up making the wrong calculation when enabling the vertical scrollviewer.
This problem occurs specifically in UWP, Windows 10.
Through investigation, it was discovered that when using fixed values
The component behaves properly, but this approach is problematic because it does not know the fixed size of the content.
The correct way is to use it the way Microsoft itself uses it:
Steps to reproduce the bug
Bug:
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.2
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response
The text was updated successfully, but these errors were encountered: