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

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

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 20 Mar 2009 23:16:51 +0000 (UTC)
To: "Michael A. Puls II" <shadow2531@gmail.com>
Cc: public-html@w3.org
Message-ID: <Pine.LNX.4.62.0903202314220.2835@hixie.dreamhostps.com>
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,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 20 March 2009 23:17:30 UTC

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