You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
It's rather straightforward to work around this issue by creating a descendant of Picker and minimally modifying its renderer but the reason for the original decision simply escapes me.
Steps to Reproduce
Use a Picker.
Set its Title.
Run on UWP.
Basic Information
Version with issue: current
Last known good version: none
The text was updated successfully, but these errors were encountered:
The Title property seemed to map more naturally to the ComboBox.Header property than the ComboBox.PlaceholderText property. Especially in the case of pre-filled data, where the PlaceHolderText would never be visible to the user, so the purpose of the form field would not be apparent.
It's rather straightforward to work around this issue by creating a descendant of Picker and minimally modifying its renderer
In a cross-platform world, I want my android and iOS and UWP apps to behave roughly the same without having to make custom renderers for each one to ensure they do.
2 years later, this is still the same and we still have to put in a special renderer to make the UWP app show the text in the placeholder bit just like iOS and Android.
Description
According to the documentation (https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.picker.title?view=xamarin-forms#Xamarin_Forms_Picker_Title),
Title
is displayed differently. Actually, it's rendered as aControl.Header
on UWP. Is there any specific reason for this? The combobox thePicker
is rendered with has a properPlaceholderText
property and it functions flawlessly. Why isn't it used?It's rather straightforward to work around this issue by creating a descendant of
Picker
and minimally modifying its renderer but the reason for the original decision simply escapes me.Steps to Reproduce
Basic Information
The text was updated successfully, but these errors were encountered: