627409 - Implement dispatchFormInput and dispatchFormChange

Status: RESOLVED WONTFIX

(Core :: DOM: Core & HTML, defect)

Description

[Mounir Lamouri (:mounir)]

I think we should now implement formInput and formChange events but I feel weird with dispatchFormInput and dispatchFormChange. The use case seems really small and very "edgy" (like initializing an output which get updated onFormChange).
Is that really worth implementing them?

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

dispatchFormInput and dispatchFormChange are indeed very strange. Do you happen to
know why they were added to HTML5?

Comment 2

[Mounir Lamouri (:mounir)]

(In reply to comment #1)
> dispatchFormInput and dispatchFormChange are indeed very strange. Do you happen
> to
> know why they were added to HTML5?

Not really. I only got this from Hixie:
[18:59] < Hixie> mostly the use case for dispatch* is to make it easier to just 
                 write the logic once in an event handler and make sure it 
                 triggers in all the various cases it could trigger
[18:59] < Hixie> but certainly the use cases for dispatch* are less than the 
                 use cases for the events themselves

IMO, given that we were very close to not support formInput and formChange, we should not bother with dispatchFormInput and dispatchFormChange.

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

There has been some new discussion @
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129

Comment 4

[Mounir Lamouri (:mounir)]

WONTFIX, per w3c bug.

Comment 5

[Eric Shepherd [:sheppy]]

Removing doc needed since these will not be added.