Re: [whatwg] Improve select required

2010-11-16 Thread Mikko Rantalainen
2010-11-16 04:16 EEST: Ian Hickson: > On Thu, 12 Aug 2010, Mikko Rantalainen wrote: >> A possible use case where this feature could be useful already (and >> cannot be fulfilled with @required): >> >> 1) An user is trying to register a new user account on some system >>and uses "foo" as the nic

Re: [whatwg] Improve select required

2010-11-15 Thread Ian Hickson
On Thu, 12 Aug 2010, Mikko Rantalainen wrote: > 2010-08-11 12:31 EEST: Jonas Sicking: > > On Wed, Aug 11, 2010 at 2:03 AM, Mikko Rantalainen > > wrote: > >> Stuff I don't want to see (combined with @required): > >> > >> - first option is always special > >> - empty string as the value is special >

Re: [whatwg] Improve select required

2010-09-13 Thread Jesse McCarthy
On Monday 13 Sep 2010 Mounir Lamouri wrote: 2. Introduce a placeholder boolean attribute for and select elements will suffer from being missing if there are no options selected or selected options all have the placeholder attribute set. I also wonder if that would be more straighforward. I s

[whatwg] Improve select required

2010-09-12 Thread Mounir Lamouri
Hi, I am glad that select required has been accepted and introduced in the specifications. However, I have the feeling we could try to improve that feature. Currently, if multiple is set or size>1, having no option selected make the element suffering from constraint validation. If multiple is not