Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pikaday: A friendly guide to front-end date pickers

pikaday.dbushell.com

Post reply on HN
Print view View original

11–20 of 146 posts

Re: Pikaday: A friendly guide to front-end date pickers

#11

Post by cryptoz »

kmoser wrote: post #4

> Travel booking often has a fixed schedule with limited time options, such as every 15 minutes. Relative dates like “Today” and “Tomorrow” can be easier to understand. Except when you're booking a flight and you're not sure whether "today" is based on your local time, the server's local time, or GMT. (I often book flights right about midnight and find words like "today" and "tomorrow" to be completely confusing.)

Montreal public transit times used to be on some kind of like, 28-hour clock. Bus times after midnight would be labelled 27:30 or something. Suuuper confusing. It sounds so bizarre in fact, that I'm doubting my memory a bit, but I'm certain it was like that (say around 2006 or so).

Re: Pikaday: A friendly guide to front-end date pickers

#12

Post by evertheylen »

cryptoz wrote: post #11
kmoser wrote: post #4

> Travel booking often has a fixed schedule with limited time options, such as every 15 minutes. Relative dates like “Today” and “Tomorrow” can be easier to understand. Except when you're booking a flight and you're not sure whether "today" is based on your local time, the server's local time, or GMT. (I often book flights right about midnight and find words like "today" and "tomorrow" to be completely confusing.)

Montreal public transit times used to be on some kind of like, 28-hour clock. Bus times after midnight would be labelled 27:30 or something. Suuuper confusing. It sounds so bizarre in fact, that I'm doubting my memory a bit, but I'm certain it was like that (say around 2006 or so).

This is actually how GTFS (a standard format for public transit data) works: https://gtfs.org/documentation/schedule/reference/#stop_time... . Especially sleeper trains can get weird with 30+ hours. But I don't think it's wise to show that to the user

Re: Pikaday: A friendly guide to front-end date pickers

#13

Post by recursive »

sureglymop wrote: post #6

My take is that Date, Time and DateTime pickers are not enough. I want month pickers. Week pickers, custom interval pickers and then some. I really dislike how limited the selection of native form elements is.

Do you think there is anything missing from or other than Firefox support?

Re: Pikaday: A friendly guide to front-end date pickers

#14

Post by 1718627440 »

TheSisb2 wrote: post #3

Native datepickers fall apart when you need to handle different date formats as user preferences (not as browser default)

The browser, called the User Agent (UA), IS the program the user uses to interact with a website according to his preferences.

Re: Pikaday: A friendly guide to front-end date pickers

#15

Post by thoughtpalette »

nhumrich wrote: post #8
carlosjobim wrote: post #2

They are wrong. Most OS native date pickers are very bad from a usability perspective. A javascript date picker fixes these issues, and allows more functions. And why are they arguing against their own product? Even making up bogus claims that using js date pickers would be illegal in Europe?

From the GitHub project: > Pikaday was started before 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

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

Re: Pikaday: A friendly guide to front-end date pickers

#16

Post by ChadNauseam »

cryptoz wrote: post #11
kmoser wrote: post #4

> Travel booking often has a fixed schedule with limited time options, such as every 15 minutes. Relative dates like “Today” and “Tomorrow” can be easier to understand. Except when you're booking a flight and you're not sure whether "today" is based on your local time, the server's local time, or GMT. (I often book flights right about midnight and find words like "today" and "tomorrow" to be completely confusing.)

Montreal public transit times used to be on some kind of like, 28-hour clock. Bus times after midnight would be labelled 27:30 or something. Suuuper confusing. It sounds so bizarre in fact, that I'm doubting my memory a bit, but I'm certain it was like that (say around 2006 or so).

I've seen this in Japan as well. A store that's open from, let's say, 8am to 1am will actually advertise itself as being open from 8am to 25pm. I guess the perception is that it's confusing to have a range where the smaller number comes before the bigger number.

Re: Pikaday: A friendly guide to front-end date pickers

#17

Post by macintux »

1718627440 wrote: post #14
TheSisb2 wrote: post #3

Native datepickers fall apart when you need to handle different date formats as user preferences (not as browser default)

The browser, called the User Agent (UA), IS the program the user uses to interact with a website according to his preferences.

Maybe. How many users change the defaults, or even know it’s an option?

Re: Pikaday: A friendly guide to front-end date pickers

#18

Post by BhavdeepSethi »

From what I've learned, be as explicit as possible when users enter dates.

We had to change our date of birth field in the user sign-up to three separate "Month Name","Day" and "Year" drop downs, since so many people made mistakes (fat finger/ swap month and day) from the "MM/DD/YYYY" field, and would then send support ticket to update it.

Post reply on HN