Bug 112247 – Calendar UI - settings current value

• Status: UNCONFIRMED
• Component: Forms

[Bronislav Klucka]

Current UI
http://peter.sh/files/webkit-calendar-3.png
contains dot button (between listing buttons) which fills current date/month/week on click, but it works only partialy in datetime-local, time part is not set.

[Keishi Hattori]

This is working as I intended. How do you want it to work?

[Bronislav Klucka]

(In reply to comment #1)
> This is working as I intended. How do you want it to work?

To set up current local time as well

[Keishi Hattori]

(In reply to comment #2)
> (In reply to comment #1)
> > This is working as I intended. How do you want it to work?
> 
> To set up current local time as well

I've thought about it but I didn't do that for a few of reasons.
1. I don't think people will be using <input type=datetime-local> to enter the current time. (Probably because the current time changes rapidly.)
2. The calendar picker is clearly an interface to choose a date. Some users won't expect that.
3. Setting the current time could do harm when the user has already chosen a time and wants to pick a date.

The most important reason is #1, use case. Do you have a specific use case where it will be useful?

[Bronislav Klucka]

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > This is working as I intended. How do you want it to work?
> > 
> > To set up current local time as well
> 
> I've thought about it but I didn't do that for a few of reasons.
> 1. I don't think people will be using <input type=datetime-local> to enter the current time. (Probably because the current time changes rapidly.)
> 2. The calendar picker is clearly an interface to choose a date. Some users won't expect that.
> 3. Setting the current time could do harm when the user has already chosen a time and wants to pick a date.
> 
> The most important reason is #1, use case. Do you have a specific use case where it will be useful?

#3 can by avoided (I'm not WebKit programmer, but I suppose it can be)
#2 calendat picker is UI to select datetime part of UI's type (sometimes date, sometimes week, sometimes month) some user's may not expect that, but appearently I did not expect that it does not fill time :)
#1 "Publish article" is one example, I want my article to be published right now. I want current time to be displayed. (Sure, I can leave it empty and on backend use current datetime if this value is empty, but every time I use this flow I have to explain this to users: "you do not have to fill that for current datetime", It would be usefull not have to do that, fill or no fill, I will deal with that, leave it empty or hit one button to fill current)

but I my case the most important is actually #2 a did not expected that... seems inconsistent. I thought someone overlook it. But as this bug says, I do not consider it a bug, but an enhancement.