W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2004

[whatwg] The type mismatch validity flag

From: Brian Wilson <brian@opera.com>
Date: Wed, 08 Dec 2004 07:27:03 +0100
Message-ID: <opsioevdps87i379@toshistation2.attbi.com>

A while back I had created a number of WF2 test cases that checked the
type mismatch validity flag by setting initial values contrary to a  
widget's
type.

In section 2.18, the following is found:

For value attributes that are invalid according to the type attribute
    The attribute must be ignored. It will appear in the DOM for the
    defaultValue attribute, but will not be used as the value of the  
control.
    The control will therefore initially be empty.

This would seem to indicate that a type mismatch validity flag condition
can only be triggered by *manual* widget input. I'm not sure if that
distinction should be noted in the spec anywhere, or of what use it
would be to page authors or UA creators to raise this point.

It does make several of my automated test cases unusable though. Drat. 8-}

-Brian

-- 
Brian Wilson
Opera Core QA
Received on Tuesday, 7 December 2004 22:27:03 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:38 UTC