Describe the bug
TeachingTip will block some text content on the second occurrence.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
Work well
Screenshots
Version Info
NuGet package version:
Microsoft.UI.Xaml 2.2.190917002
| Windows 10 version | Saw the problem? |
| :--------------------------------- | :-------------------- |
| Insider Build (xxxxx) | |
| May 2019 Update (18362) | Yes |
| October 2018 Update (17763) | |
| April 2018 Update (17134) | |
| Fall Creators Update (16299) | |
| Creators Update (15063) | |
| Device form factor | Saw the problem? |
| :-------------------- | :------------------- |
| Desktop | Yes |
| Mobile | |
| Xbox | |
| Surface Hub | |
| IoT | |
Additional context
I think I saw this during development but it went away with a selfhost update. I suspect it is a rendering bug, if I recall correctly the live visual tree seemed to think nothing was wrong.
I have the problem that no content is displayed at all at the second time, when IsLightDismissEnabled is true.
I had this happen with the XAML Controls Gallery. It is clipping some of the text, but not the first time it comes up. Only subsequent opens. When I restart the app, it works again the initial time, and fails afterwards.
(In my own application, it did seem to be visually worse when IsLightDismissEnabled
was true
, which surprises me just a little, because that behavior doesn't seem related to the display of the control.)
Same as @rbwhitaker
With the newer preview versions I don't have any problems anymore.
if Target={x:Bind Something} is used, text will be blocked
If you hover your mouse on the TeachingTip with Visual Studio XAML Enable Selection, the content will show properly
@jp-weber I used prerelease version, it still not work well as I expected
@gegao18 can you please help debug this issue ? @StephenLPeters has looked at it and can provide more context/repro.
In the latest pre-release version, this problem still exists and has not been fixed @ranjeshj @gegao18 @StephenLPeters
@gegao18 looked at it and found that this is likely an issue in the composition stack. Still being investigated...
The issue in the Composition code has been found and fix. The fix will be in a future release of Windows, but will also be part of WinUI 3. The workaround done for #2305 will cover other down-level scenarios in the meantime.
Most helpful comment
The issue in the Composition code has been found and fix. The fix will be in a future release of Windows, but will also be part of WinUI 3. The workaround done for #2305 will cover other down-level scenarios in the meantime.