omghb

Workaround: ```C# using OpenQA.Selenium.Appium.ImageComparison; using System; using System.Collections.Generic; using System.IO; using System.Linq; using System.Reflection; namespace AppiumWrapper { public static class ComparisonResultHelper { // Workaround for https://github.com/appium/appium-dotnet-driver/issues/463 public static void FixedSaveVisualizationAsFile(this...

@samhouts - The issue #6580 sounds similar to this one but I believe that they are different when looking at the details. - In my opinion there is a bug...

In my opinion it is not a valid workaround to get every user reconfigure the default system keyboard. Furthermore, I want to repeat that this is a XAMARIN BUG in...

Please fix this. I run into the same issue. Workaround `false` helped.

We run into the exact same issue that our `TemplateBinding` for a `Border.CornerRadius` does not work anymore after updating MAUI to version 8.0.20. Regression issue: - Version it still worked:...

We see this issue in our App as well with MAUI version **7.0.92**. Because of this we cannot use the `On().SetUseSafeArea(false);` setting right now.

@mattleibow The keyboard "next" button is working on Android as expected but the code line ``` Console.WriteLine("Hidden entry: IsVisible: " + hiddenEntry2.IsVisible); ``` returns `true` on Android as well. This...

> @omghb no, it shouldn't be false. IsVisible on parent stops its rendering and rendering of children, but it doesn't change their properties. @cucumber-sp That's not what I would expect....

@bradencohen The `Visibility` property returns the same value as `IsVisible`. The element is hidden and should be `Collapsed`. 

Thanks for the improvement in MAUI 8.0.10: - #20160 Unfortunately, this fixes the issue only partly. Still not working: - Hide an element that has the focus - Expected: next...