-
Notifications
You must be signed in to change notification settings - Fork 102
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
TeachingTip shows an addional white rectangle popup on Linux #634
Comments
I tested this in a new Avalonia 11.1.0 project without FluentAvalonia and the Edit: Everything below is wrong. Still investigating.
Converting #635 to draft for now. I suspect the real root cause is in |
Turns out it has nothing to do with .NET versions, not sure how did I think it's related to dotnet versions. I have updated the issue description. #635 should be a reasonable fix. |
Describe the bug
<PropertyGroup><AvaloniaVersion>11.2.0</AvaloniaVersion></PropertyGroup>
toFAControlsGallery.Desktop.csproj
dotnet run --project samples/FAControlsGallery.Desktop/FAControlsGallery.Desktop.csproj
TeachingTip
and click button.Screenshots
Desktop/Platform (please complete the following information):
Additional context
300, 200
seems to be coming fromAvalonia.X11/X11Window.cs
. This bug seems to be caused by commit1cfa82ca
in Avalonia first released in11.2.0-beta1
.Old incorrect bug description for archival purpose
Describe the bug
TargetFramework
ofFAControlsGallery.Desktop.csproj
fromnet8.0
tonet9.0
dotnet run --project samples/FAControlsGallery.Desktop/FAControlsGallery.Desktop.csproj
TeachingTip
and click button.Screenshots
Desktop/Platform (please complete the following information):
Additional context
Only reproduced on dotnet 9. It works as intended on dotnet 8.
_lightDismissIndicatorPopup.Child.Bounds
={0, 0, 0, 0}
_lightDismissIndicatorPopup.Child.Bounds
={0, 0, 300, 200}
Width
andHeight
are alwaysNaN
,DesiredSize
is always{0, 0}
300, 200
seems to be coming fromAvalonia.X11/X11Window.cs
but I'm not sure. Also I still have no idea why it behaves differently on dotnet 8 and 9.The text was updated successfully, but these errors were encountered: