-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] Shell SearchHandler blocks touch to view #10124
Comments
@davidortinau did you find a workaround? For example a way of dismissing the transparent view when the query is confirmed? I am trying to accomplish the same thing and am experiencing the same issue on iOS. |
For the moment I abandoned the SearchHandler and added a SearchBar. https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/searchbar |
Running into the same issue. Calling Unfocus() in OnQueryConfirmed doesn't seem to do anything |
Looking at |
Looks like we need to set |
any Update? |
So I am not sure what is happening with this. The fix here has been ready to go for a while but nothing is being merged it seems any more. Based on the pull request I have created my own
Seems to work for me as a workaround. |
Hello @varyamereon, I can't seem to use your solution. Can you share your complete CustomShellPageRenderer code file please ? |
Sure thing. You need a CustomShellPageRendererTracker.cs in your iOS project that looks like this:
and a CustomShellRenderer.cs that implements it also in your iOS project:
Hope that helps. Here's hoping for an official solution some day. |
Thanks @varyamereon, it works like a charm :-) |
Hey everyone! Sorry this took a while. Looking to merge this now and should be available in the next update :) |
Description
I have the following ContentPage that implements a SearchHandler to filter the CollectionView items source on the page. I set the ShowsResults to false, however there's still a view being displayed over the page preventing touches from getting to my CollectionView.
Steps to Reproduce
Expected Behavior
Everything works as it does not, but the content of the page isn't behind a partially transparent view that blocks my touches.
Actual Behavior
Touches are blocked.
Basic Information
Screenshots
https://www.screencast.com/t/hciTVvHnU
Reproduction Link
https://github.com/davidortinau/wpbf/tree/bugs/search/WhitePaperBible
The text was updated successfully, but these errors were encountered: