> Second, we need to start using built-in browser inputs instead of downloading megabytes of JS to render something like a datepicker Then built-in browser inp

> Second, we need to start using built-in browser inputs instead of downloading megabytes of JS to render something like a datepicker Then built-in browser inputs need to offer customization, which the more complicated ones often do not. Other than datepickers, most inputs are native by need of accessibility. > There are now input fields for everything, but I rarely see them used iOS Safari currently does not support most of the native datepicker API, rendering it almost useless.