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
This is because browsers don't have native pickers for year-only, and several other types of "dates" we support. Rather than risking that our custom picker might not work well on certain phones, we fall back to using the native picker. The date is treated the same though. It should not matter which date in a year you select. Once the field is blurred, it ought to only show the selected year.
I know this isn't optimal, and it might be the case that the custom picker would give a better user experience after all.
We could potentially add an option to force the use of custom or native picker… 🤔
Current behavior
When the year picker is loaded on a phone screen, it works as a normal date-picker instead:
When it loads on a big screen, the year picker works as expected:
Steps to reproduce the behavior:
Expected behavior
Environment
The text was updated successfully, but these errors were encountered: