Bug 21788 - Autocomplete on Searchbar
Summary: Autocomplete on Searchbar
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-08-03 17:27 UTC by Michel Chowanski
Modified: 2016-03-16 11:56 UTC (History)
5 users (show)

Tags: ac android functional searchbar
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Michel Chowanski 2014-08-03 17:27:08 UTC
I use a SearchBar:

<SearchBar x:Name="AttractionSearchBar" Placeholder="Attraktion suchen ..." SearchButtonPressed="OnAttractionSearchBarPressed" />

Android give me a few suggestions, when I'm typing a word to search (like here: http://blog.checklist.com/wp-content/uploads/sites/3/2014/06/autocomplete1.png). That's cool - but if I click at one suggestion, the hole text will be removed and I have to type the word again. That's very annoying ...

Tested on Samsung Galaxy S3 Mini. Can you fix it?
Comment 1 Seth Rosetter 2015-06-01 14:17:13 UTC
Confirmed in Xamarin.Forms 1.4.2 using a Samsung Galaxy Note 4, Android 5.0.1
Comment 3 Jason Smith [MSFT] 2016-03-16 11:56:36 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team