[prev in list] [next in list] [prev in thread] [next in thread] 

List:       whatwg
Subject:    Re: [whatwg] Form Validity Ambiguity - patternMismatch
From:       Joseph Pecoraro <pecoraro () apple ! com>
Date:       2010-04-20 16:37:05
Message-ID: F249774B-F392-4D10-BC00-C261307BA9EE () apple ! com
[Download RAW message or body]

On Apr 20, 2010, at 6:16 AM, Mounir Lamouri wrote:

> Actually, if you are looking for something more normative (the table =
is
> non-normative), at the end of each input element states description, =
you
> can found the list of attributes which apply/don't apply. AFAIK, the
> attributes/methods never mention in which states they apply. I suppose
> it is to prevent mentioning things twice thus doubling the needed
> changes and the chances of incoherence/mistakes.

You're correct! Thanks for pointing out that section. I still think this =
could
be clarified. I feel that a majority of the time someone is going to =
read
patternMismatch and say "oh, I just need a pattern attribute" and not =
think
to check that the pattern attribute only applies to particular types.
Does anyone else agree or should this be left alone?

- Joe=

[Attachment #3 (unknown)]

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; "><div><div>On Apr 20, 2010, at 6:16 AM, \
Mounir Lamouri wrote:</div><div><br></div><blockquote type="cite"><div>Actually, if \
you are looking for something more normative (the table is<br>non-normative), at the \
end of each input element states description, you<br>can found the list of attributes \
which apply/don't apply. AFAIK, the<br>attributes/methods never mention in which \
states they apply. I suppose<br>it is to prevent mentioning things twice thus \
doubling the needed<br>changes and the chances of \
incoherence/mistakes.<br></div></blockquote><div><br></div><div>You're correct! \
Thanks for pointing out that section. I still think this could</div><div>be \
clarified. I feel that a majority of the time someone is going to \
read</div><div>patternMismatch and say "oh, I just need a pattern attribute" and not \
think</div><div>to check that the pattern attribute only applies to particular \
types.</div><div>Does anyone else agree or should this be left \
alone?</div></div><br><div>- Joe</div></body></html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic