3 ms·
Omg yes, I thought I was crazy when I was pushing for native input type=date instead of JS date picker, it worked perfectly with minimal configuration on my pho
by abustamam 1y ago
Omg yes, I thought I was crazy when I was pushing for native input type=date instead of JS date picker, it worked perfectly with minimal configuration on my phone and on my Mac, but then my coworkers said it didn't work for them on their browsers, turns out, yeah, it's not consistent.
I then proceeded to spend the next week crying trying to get JS date picker to work as well as native did on my browsers.
- Muromec 1y agoOn all the projects I worked that involved ui elements library, datepicker consistently was the biggest pain in the ass, rivaled only by modals.
- dawnerd 1y agoModals at least are a solved problem these days.
- VladVladikoff 1y agoWait which browsers can’t support html5 date field?
- abustamam 1y agoIt's not a question of support, it's a question of consistency. I don't remember the details, I just remember it was barely usable on one of my coworkers device/browsers. It worked, for some definition of the word, but it was not intuitive. https://caniuse.com/input-datetime https://caniuse.com/input-datetime
- speleding 1y agoIt's the one place we still use user-agent sniffing: if the built in date picker works we show that (iPhone / iPad), otherwise we do a JS picker.