[Approved] Add a behavior (or attached property) to allow users the ability to close the soft keyboard when clicking outside of a view

[PureWeen]

There are a number of users that want to be able to tap into the nothingness and close the soft keyboard.

dotnet/maui#12002 (comment)

We didn't copy this behavior over from XF because the mechanism used to implement this behavior was to make the PageRenderer focusable/clickable which wreaked havoc on accessibility.

I have a proposal here for some APIs we could add to MAUI
dotnet/maui#12003
dotnet/maui#11983

I feel like this type of behavior should live inside the community toolkit, so it can be refined and added to out of band from the MAUI. We can release these initial features inside a NET 7 version of the community toolkit. Since this is added on behavior it seems like it would survive and iterate better inside the toolkit vs inside the core code.

The core MAUI code just needs to provide the APIs necessary to enable this type of feature.

I already have a behavior built here
https://github.com/PureWeen/ShanedlerSamples/tree/main/ShanedlerSamples/Library/TapToCloseBehavior
and the iOS code can be easily removed from MAUI core and put into a behavior as well.

            <Entry Placeholder="Text Field" Text="Starting text" WidthRequest="300">
                <Entry.Behaviors>
                    <local:SoftKeyboardBehavior CloseOnTapOutsideBounds="true"></local:SoftKeyboardBehavior>
                </Entry.Behaviors>
            </Entry>

[rachelkang]

I agree! Let's introduce these behaviors in toolkit to enable our developer community while preserving and continually encouraging accessibility

[pictos]

@PureWeen, so far this issue only happens on android?

[pictos]

Great, the API spec will be the same as on dotnet/maui#11983?

[PureWeen]

I think eventually yes.
That would be some additional features that could be added.

The initial spec could include a couple of those as well but my thinking for the first version of this could just be something like

            <Entry Placeholder="Text Field" Text="Starting text" WidthRequest="300">
                <Entry.Behaviors>
                    <local:SoftKeyboardBehavior CloseOnTapOutsideBounds="true"></local:SoftKeyboardBehavior>
                </Entry.Behaviors>
            </Entry>

And then it could grow to include the APIs talked about here as well.

[PureWeen]

So, the first feature would be this
dotnet/maui#12003

Once that's merged and created then we could look at adding additional features like this
dotnet/maui#11983

[pictos]

@PureWeen how can we implement the interface on our side and make that work on Entry? Should we create a custom Entry that implements that interface or that can be done with AttachedProperty?

[PureWeen]

The interface isn't really needed.

We'd only do an interface if this was made part of MAUi.Core

[pictos]

I approve this feature ✅

[CliffAgius]

Closed as per the Community Stand-up discussion here: https://youtu.be/N9wMcBP4jtg?t=2889