W3C home > Mailing lists > Public > public-html@w3.org > March 2009

Re: [forms] Detailed review of the DOMControlValueChanged and 'input' events

From: Michael A. Puls II <shadow2531@gmail.com>
Date: Fri, 20 Mar 2009 22:31:50 -0400
To: "Ian Hickson" <ian@hixie.ch>
Cc: public-html@w3.org
Message-ID: <op.uq4encas1ejg13@sandra-svwliu01>
On Fri, 20 Mar 2009 19:16:51 -0400, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 2 Dec 2008, Michael A. Puls II wrote:
>> > >
>> > > 2. Also, I'm unsure what controls support the input event (and
>> > > oninput=""). I see a table that has some 'yes' for different types
>> > > of <input> elements, but I don't see it specified for others. Is
>> > > 'input' supposed to fire for all form controls unless specified
>> > > otherwise? Or, are you trying to limit it to most types of <input>
>> > > and just <textarea> (as in, not for <select>)?
>> >
>> > It indeed doesn't apply to <select> right now.
>>
>> Opera is the only one that supports it on <select>. Opera supports it on
>> checkboxes and radio buttons too. This is probably because WF2 basically
>> talked about 'input' as a change on any form control.
>>
>> > Should it?
>>
>> Not sure. I know nothing that depends on it for <select> except for some
>> test caases.
>
> I haven't changed the spec, so input still doesn't fire on <select>.
> Please let me know if this proves problematic.
>
> Cheers,

Will do.

-- 
Michael
Received on Saturday, 21 March 2009 02:32:28 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:43 UTC