[nhumrich]

From the GitHub project:

> Pikaday was started before <input type="date"> was supported in browsers and before custom elements and component frameworks. Pikaday is probably not the right choice today

The project itself has been deprecated

[thoughtpalette]

This should be higher up. Posting a deprecated library with this title is an interesting choice.

[phil-pickering]

You're all getting a little confused!

This is an up-to-date guide demonstrating why the old deprecated Pikaday JavaScript Datepicker is no longer needed.

[dbushell]

yep! I decided to repurpose the pikaday.com domain because it was still seeing a lot of traffic despite the project being unmaintained for years.

[culi]

Did you click on the OP? This whole post is about using native date pickers. The very first words are:

> Who needs a JavaScript date picker?

> The answer, in most cases, is nobody!

[foresterre]

I was quite confused too. I thought these were Pikaday implementations, partly because I usually use UK language in browsers, and then you get exclusively these (annoying to me) AM/PM date input pickers, and this time I didn't.

I tried some of the inputs and found that they worked well for initial input, but editing inputs didn't (e.g. the masked date input cursor just jumps over previous decimals, when typing a new number)

I made a reproduction video and tried to report it to the Pikaday issue tracker after which I found out it's deprecated.

Going back, and comparing the readme with the page, does show that the post uses native inputs. ... I feel that could have been more explicit; in this post I expected Pikaday to have the option to use native pickers with some component styling.