Bug 59550 - Changing Entry Placeholder from Focused handler results in keyboard disappearing on Android
Summary: Changing Entry Placeholder from Focused handler results in keyboard disappear...
Status: RESOLVED DUPLICATE of bug 32600
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-09-18 10:25 UTC by John Hardman
Modified: 2017-09-18 13:39 UTC (History)
3 users (show)

Tags: Android Entry Placeholder Focused
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 John Hardman 2017-09-18 10:25:46 UTC
Using the following code on Android using XF, when the user taps on the Entry, the soft keyboard disappears.

            Entry entry = new Entry
                Placeholder = "Placeholder for Entry"
            entry.Focused += (object sender, FocusEventArgs e) =>
	            entry.Placeholder = entry.Placeholder + ">";

May be related to https://bugzilla.xamarin.com/show_bug.cgi?id=32600
Comment 1 Paul DiPietro [MSFT] 2017-09-18 13:39:03 UTC
They both run using the same control (FormsEditText) so it would almost certainly be directly related. I will mark this as a duplicate and update the title of the other bug to reflect that both are affected.

*** This bug has been marked as a duplicate of bug 32600 ***