On Thu, 20 Jan 2011, Olli Pettay wrote:
On 10/22/2010 10:09 PM, Jonas Sicking wrote:
On Fri, Oct 22, 2010 at 11:15 AM, Erik Arvidssona...@chromium.org wrote:
On Oct 22, 2010 2:00 AM, Anne van Kesterenann...@opera.com wrote:
Yeah, I don't mind moving these features to libraries. Anyone
On 10/22/2010 10:09 PM, Jonas Sicking wrote:
On Fri, Oct 22, 2010 at 11:15 AM, Erik Arvidssona...@chromium.org wrote:
On Oct 22, 2010 2:00 AM, Anne van Kesterenann...@opera.com wrote:
Yeah, I don't mind moving these features to libraries. Anyone implemented
them apart from Opera?
Neither
I agree with Erik, the generic feature probably is not worth the simple use
case. It can (and probably should) be easily implemented by the developer in
his form logic when needed.
Sergey/
On 21 October 2010 22:56, Erik Arvidsson a...@chromium.org wrote:
The forminput and formchange events
On Fri, 22 Oct 2010 10:55:24 +0200, Sergey Ilinsky ser...@ilinsky.com
wrote:
I agree with Erik, the generic feature probably is not worth the simple
use case. It can (and probably should) be easily implemented by the
developer in his form logic when needed.
Yeah, I don't mind moving these
On Oct 22, 2010 2:00 AM, Anne van Kesteren ann...@opera.com wrote:
Yeah, I don't mind moving these features to libraries. Anyone implemented
them apart from Opera?
Neither WebKit nor Gecko implements it:
https://bugs.webkit.org/show_bug.cgi?id=26141
On Fri, Oct 22, 2010 at 11:15 AM, Erik Arvidsson a...@chromium.org wrote:
On Oct 22, 2010 2:00 AM, Anne van Kesteren ann...@opera.com wrote:
Yeah, I don't mind moving these features to libraries. Anyone implemented
them apart from Opera?
Neither WebKit nor Gecko implements it:
On Fri, Oct 22, 2010 at 12:09, Jonas Sicking jo...@sicking.cc wrote:
This means that we should also remove
dispatchFormInput/dispatchFormChange from the HTML5 spec, right?
That was my intention and the subject hints at that. Sorry for not
including it in the body as well.
--
erik
On Fri, 22 Oct 2010 21:31:32 +0200, Erik Arvidsson a...@chromium.org
wrote:
On Fri, Oct 22, 2010 at 12:09, Jonas Sicking jo...@sicking.cc wrote:
This means that we should also remove
dispatchFormInput/dispatchFormChange from the HTML5 spec, right?
That was my intention and the subject hints
The forminput and formchange events are dispatched on all resettable
elements in a form when any element associated with the form
dispatches an input or a change event.
Is this case really worth the cost of increasing the size of the API
when it can easily be achieved with capturing events?
erik