I find that most datepickers are better than the browser's default. It's a shame that they can't be styled more

joenot443 2 minutes ago | parent | next [-]

I agree.

The date range selector used in Google Flights is a near flawless control. The implementation can be done, it’s just hard.

▲

paularmstrong 3 hours ago | parent | prev | next [-]

I agree with a caveat: Default date pickers on mobile devices are very good. But on desktop browsers they are terrible. They break design continuity in a very ugly way and have quirks between browsers and systems. And personally, the popup calendar they provide just too small. If the system took over the date picker on desktop like it does on mobile devices instead of forcing the browser to handle it, I feel like we could get somewhere better.

	▲	king_geedorah 3 hours ago \| parent [-]
		I just went and confirmed this because it’s not something I’ve really looked at and I agree. The date picker you get from a straight up <input type=“date”> on iOS webkit is pretty nice. The one in webkit on macOS isn’t quite as good, but is better than the one in firefox if only because firefox closes the picker when you type a year in to move far through time. Good thing firefox is open source.

▲

julianozen 3 hours ago | parent | prev | next [-]

Yes, but having worked on the date picker at Airbnb I can assure you almost every custom implementation (probably ours too!) messes up date picking in some region in an important way

▲

neals 3 hours ago | parent [-]

Except...?

	▲	ceejayoz 3 hours ago \| parent [-]
		There’s no except. They all suck in some specific way.

▲

pwdisswordfishs 3 hours ago | parent | prev [-]

> I find that most datepickers are better than the browser's

You mean your browser's. There is no "the browser".

	▲	Shellban 2 hours ago \| parent [-]
		The Google Chrome team would like a word with you.