-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] iOS DatePicker with UIDatePickerStyle.Inline missing month information #13593
Comments
Hi, @mos379 - thanks for submitting this issue! Have you tried running on other versions of iOS? If it looks different, would you be able to share relevant screenshots? Also, if you could share your project or a sample project reproducing this issue, that would be incredibly helpful in helping us to better understand the issue. Thank you! :) |
I attached the sample project. I'm currently not able to test on a different OS version |
I came across the same issue the day I updated iOS app to Xamarin.Forms 5.0.0.1874. Build 5.0.0.1874 'forced' the UIDatePickerStyle.Automatic, which is same as .Compact. The .Automatic look and feel is quite ugly, and confusing for the end user. I implement a Custom renderer for unrelated Date issue #13366, so I tried the .Inline style - not usable. |
@mos379 thanks for the sample and @mikebikerider thanks for sharing! |
Hi all, I am also experiencing this. Any workaround for the moment? With a renderer of some sort. Thank you very much |
@rachelkang any update on this issue? |
Any update so far?. I also experiencing the same. Thanks to @mikebikerider , by using .automatic style , can solve this issue, but the .automatic behaviour was not what i expected. |
Any Update on this issue? I also facing same issue in .inline style. |
I am also facing the same issue in the .inline style But I fixed it @mikebikerider @jsuarezruiz @rachelkang @nagurbee @gil-rodrigues @Alhaadi-IDB @mos379 |
Just posting a link where there is a picture does not help @Sohel3798 ! |
Description
When changing the presentation of the DatePicker to UIDatePickerStyle.Inline on iOS the presentation is not sized correctly and cuts of the month and Year info
Steps to Reproduce
Expected Behavior
showing correct inline calendar with month and year info
Actual Behavior
only showing days with a fragment of the top info
Basic Information
Screenshots
Related issue: #11963
The text was updated successfully, but these errors were encountered: