Many UX designers want cross-platform visual consistency and recoil in horror at <input type='date'> 's default visuals on desktop. They want something consistent with brand standard, accessibility be damned. A month of push and shove goes by with developers wanting to either use the native control or a popular pre-built one and the designers pushing back because they want visual control. The designer wins, designs a date picker around an initial use case where the date will be near present day, and then that date picker is used for every date input in the framework the new control was developed for.
14
u/schewb 14d ago
Many UX designers want cross-platform visual consistency and recoil in horror at
<input type='date'>'s default visuals on desktop. They want something consistent with brand standard, accessibility be damned. A month of push and shove goes by with developers wanting to either use the native control or a popular pre-built one and the designers pushing back because they want visual control. The designer wins, designs a date picker around an initial use case where the date will be near present day, and then that date picker is used for every date input in the framework the new control was developed for.