Bug 38001 - Picker controls on Windows showing incorrect info and incorrectly scrolled list
Summary: Picker controls on Windows showing incorrect info and incorrectly scrolled list
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jason Smith [MSFT]
Depends on:
Reported: 2016-01-25 17:26 UTC by John Hardman
Modified: 2017-03-04 12:23 UTC (History)
3 users (show)

Tags: Windows Picker DatePicker TimePicker scrolling
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 for Bug 38001 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description John Hardman 2016-01-25 17:26:38 UTC
When debugging the Windows 8.1 build of app on local machine running Windows 10, pickers work (largely) as expected.

However, when debugging using VS2015 Remote Debugger on other devices (tested on Linx tablet running Windows 10 and Lenovo notebook running Windows 8.1), the pickers when expanded show information incorrectly. Often there is an extra blank item in the list, the list is not in the expected order, the list is scrolled so that the top is not visible, and scrolling is inoperable.

This occurs on Pickers, DatePickers and TimePickers.

The same problem occurs if a release build is done and deployed, rather than just when using the Remote Debugger.

All three devices used for testing report Device.Idiom = Tablet.
Comment 1 Paul DiPietro [MSFT] 2017-03-03 16:13:07 UTC
I know this issue has been sitting around for a while and seems like an odd one. Aside from anything changing in the interim, there were also some recent changes to bindings on the Picker which I think would be available in the nightly by this point. I wonder if this is still occurring, and if has there been any particular scenario that causes it to occur (as you used the word often), or if it's just a bit random?
Comment 2 John Hardman 2017-03-04 12:23:11 UTC
@Paul_DiPietro - Yes, it's still a problem.

Without using binding, I just populated a Picker with the words used in the phonetic alphabet from alpha to uniform (these are the usual standard ones, as opposed to the other standard ones used in the USA :-) )

Using a WinRT 8.1 build for x86, executed using the Visual Studio 2015 remote debugger on a Win10 laptop, simply scrolling down using the cursor keys shows alpha-uniform as expected, followed by a gap, then starts showing from the top of the list again but without the selection moving. When the last one visible at the bottom of the list is hotel, hitting cursor down again makes the list jump so that bravo is now the bottom item shown. Cursoring up does a similar thing.

With other Pickers containing less items, I do not see the problem.

With DatePicker using the same remote debugger setup, attempting to open the list of dates or months (but not years, which work) and then scroll through the list using the keyboard, the list closes immediately the selection changes. This does not happen when using a local debug session, only using the remote session.

So, overall, it's not as bad as it used to be, but using there are still some issues when using Pickers and DatePickers in a remote debug session.