Last week, I replaced 100kb of React code for a JavaScript based date picker with an <input type=datetime-local>. It's part of an accessibility project, and the old date picker wasn't good for many reasons. What a win! This input type didn't land in browsers other than Chrome until a few years ago, and my support matrix didn't officially allow me to use it until pretty recently. By and large, this is a win on paper.
Within 24 hours a customer using Firefox and NVDA (a screen reader) wrote in to say they hated the change and asked me to bring the old date picker back.
bastawhiz · · focus · HN ↗
Last week, I replaced 100kb of React code for a JavaScript based date picker with an <input type=datetime-local>. It's part of an accessibility project, and the old date picker wasn't good for many reasons. What a win! This input type didn't land in browsers other than Chrome until a few years ago, and my support matrix didn't officially allow me to use it until pretty recently. By and large, this is a win on paper.
Within 24 hours a customer using Firefox and NVDA (a screen reader) wrote in to say they hated the change and asked me to bring the old date picker back.
How am I supposed to win here?