[BUG] (WPF) When a TransitioningContentControl's initial actual width or height is 0, it throws an exception in v12.1.1 #2565
Labels
Comments
|
We are currently working on a fix for this one and should be out in the next couple days |
2 tasks
|
@TolikPylypchuk thanks for the detailed information and the reproduction. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
This is a WPF issue; I don't know whether it also applies to other platforms.
When the content presenter of a
TransitioningContentControlhas a zero actual width/height, an exception is thrown in theTransitioningContentControl.GetRenderTargetBitmapFromUiElementmethod during the initial transition. This applies to v12.1.1 only - everything works fine in v11.x.Steps To Reproduce
I've created a repository which reproduces the issue: https://github.com/TolikPylypchuk/ReactiveUIBugTransitioningControl.
The repository contains a simple window which contains a
ViewModelViewHost. By default its content is stretched, so the exception will not be thrown. But if you go toMainWindow.xamland remove theTestHost'sHorizontalContentAlignmentorVerticalContentAlignmentthen the content's actual width or height will become 0, and an exception will be thrown when binding to a view model.Expected behavior
No exceptions thrown when the initial actual width/height of the content is 0.
Environment
The issue is reproducible on .NET Core 3.1 and .NET 5 RC2.
Additional context
As a workaround, you can make sure that your
TransitioningContentControleither has an explicit size or is stretched, and stretches its content, and then control the sizing in its child controls - this worked for me, but I guess it's not always applicable.The text was updated successfully, but these errors were encountered: