Am 09.03.2011 06:51 schrieb Jukka K. Korpela:
Jonas Sicking wrote:
I'm having a little bit hard of a time figuring out what a good UI
would look like in the general case. I.e. what should the UI look like
for
input type=date id=date name=date
value=2011-04-01 list=datelist exclusive
datalist
On Tue, 8 Mar 2011 16:51:25 -0800, Jonas Sicking wrote:
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch
wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker.
Am 09.03.2011 12:19 schrieb Diogo Resende:
On Tue, 8 Mar 2011 16:51:25 -0800, Jonas Sicking wrote:
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker. Quite often, whether trying to
make dates or selling flights, there is a known set of
(non-consecutive) days that are possible, so
On Tue, 08 Mar 2011 19:46:41 +0100, Markus Ernst derer...@gmx.ch wrote:
I hope very much that this proposal will make it into the standard.
Except for date/time and color input elements, I can also imagine use
cases regarding the range element (if a part of the range is not
available).
We
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker. Quite often, whether trying to
make dates or selling
Jonas Sicking wrote:
I'm having a little bit hard of a time figuring out what a good UI
would look like in the general case. I.e. what should the UI look like
for
input type=date id=date name=date
value=2011-04-01 list=datelist exclusive
datalist id=datelist
option value=2011-04-01 label=April
