Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
With a Horizontal StackLayout that contains various controls, the last of which is an Entry control that would extend off the right-hand side of the screen if it were not contained in the StackLayout, on iOS and Android typing into the Entry results in scrolling (either the Entry or the StackLayout) that ensures the caret at which typed characters appear is always in view. On WinPhone however, scrolling does not happen, so the caret and the characters being typed can actually be off the side of the screen. This makes for a poor user experience - scrolling should happen in an Entry so that the caret is always visible.
I have checked this issue but not able to reproduce it.
Could you please provide me sample project so that I can reproduce this issue at my end.
Created attachment 11806 [details]
Csharp file that demonstrates issue
Source file that demonstrates problem described.
You will need to change the namespace to match your project, but otherwise it will run as is.
I have checked this issue with provided sample code in comment #2 and getting different behavior on iOS and Windows Phone.
Screencast for iOS: http://www.screencast.com/t/q1lP3sYhL5ro
Screencast for WindowsPhone: http://www.screencast.com/t/7qGN4gdW9X1
Please check the screencast and let me know If I have missed anything for testing this issue.
I've just given this a quick test and it looks like it has been fixed in XF 2.0.1