Implement dispatchFormInput and dispatchFormChange

RESOLVED WONTFIX

Status

()

defect
RESOLVED WONTFIX
9 years ago
9 years ago

People

(Reporter: mounir, Unassigned)

Tracking

({html5})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

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?
dispatchFormInput and dispatchFormChange are indeed very strange. Do you happen to
know why they were added to HTML5?
(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.
There has been some new discussion @
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129
WONTFIX, per w3c bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Removing doc needed since these will not be added.
Keywords: dev-doc-needed
You need to log in before you can comment on or make changes to this bug.