On Fri, Oct 1, 2010 at 10:07 PM, Mounir Lamouri <[email protected]> wrote: > On 10/01/2010 05:11 PM, Jonas Sicking wrote: >> I suggest that when pattern and multiple are both applied on a >> control, that the pattern is applied to each individual component of >> the value, rather than the value as a whole. > > That makes sense. However,this is removing some possibilities with the > pattern attribute. For example, the author wouldn't be able to ask for > different emails with at least one from company A and company B. In > addition, asking for "at least x emails", "exactly y emails" or "maximum > z emails" wouldn't be possible. > Though, the former case doesn't sound to be important and the later > would be better with new attributes like minentries and maxentries.
I suspect this is a much less common use case. I think it'd be fine to make people use javascript together with setCustomValidity() to handle that. / Jonas
