Bug 31704 - Editor and Entry behave differently on WP for the keyboard suggestions
Summary: Editor and Entry behave differently on WP for the keyboard suggestions
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.3
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-07-07 10:48 UTC by Erik Renaud
Modified: 2016-12-05 18:43 UTC (History)
5 users (show)

Tags:
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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Erik Renaud 2015-07-07 10:48:00 UTC
While using Visual Studio 2013, Xamarin Forms 1.4.3 and the WP 8.1 emulator, we are having problemes when using an Entry control in xaml vs using the Editor control.

If you put the Keyboard property to Text, the Editor controls behaves correctly and text suggestions show up immediatly. On the same page, the Entry control with the Keyboard property set to Text has weird behaviors where the suggestions do not show up immediatly.
Comment 1 Parmendra Kumar 2015-07-07 11:30:04 UTC
@Erik

I have checked this issue as provided steps mentioned in bug description but not able to reproduce this issue.
Could you please provide me a sample project? so that I can reproduce this issue at my end efficiently.

Thanks.
Comment 2 Paul DiPietro [MSFT] 2016-12-05 18:43:03 UTC
Please reopen this with a reproduction if this issue still exists in the current stable release.