Bug 58031 - Can't select all on password label
Summary: Can't select all on password label
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jimmy [MSFT]
Depends on:
Reported: 2017-07-08 16:28 UTC by Edward Brey
Modified: 2017-07-10 16:39 UTC (History)
2 users (show)

Tags: ac uwp entry password
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 Edward Brey 2017-07-08 16:28:35 UTC
When you press Ctrl+A to select all on a password label, the all characters are momentarily selected, but then immediately deselected. It looks really glitchy and makes clearing a password inconvenient.

1. Create a form with two labels, one with IsPassword="True", and one without.
2. Run the app and enter text into each label.
3. On each label, press Ctrl+A.

Result: Only the non-password label lets you select the text.
Expected: Both labels should let you select the text.

Platform observed on: UWP
Comment 1 Jimmy [MSFT] 2017-07-10 16:39:11 UTC
I was able to observe this behavior in a new project when using Forms However after updating to Forms 2.3.5-pre6 the issue appears to be resolved. 

If you continue experiencing this issue with 2.3.5-pre6 or newer, please re-open this report and attach a reproduction project so we can investigate. Thanks!