[whatwg] Form element invalid message

Scott González scott.gonzalez at gmail.com
Wed Aug 10 18:31:24 PDT 2011

2011/7/28 Scott González <scott.gonzalez at gmail.com>

> There are essentially three choices (this applies to most new markup-driven
> features):
> 1) Provide the information in the appropriate attributes and let the
> browser do its thing.
> 2) Provide the information in a script and do everything via scripting.
> 3) Provide the information in the appropriate attributes, but handle them
> via scripting.
> #1 will never be as flexible as #3. #2 is a decent compromise and can be
> made more flexible by allowing additional configuration via scripts. I think
> the spec needs to make #1 as good as it can, but also do what it can to
> encourage #2 over #3 where possible/reasonable.

I just noticed that I transposed #2 and #3 everywhere. We want to encourage
#3 is a decent compromise that we want to encourage over #2.

More information about the whatwg mailing list