Closed
Bug 627409
Opened 14 years ago
Closed 14 years ago
Implement dispatchFormInput and dispatchFormChange
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mounir, Unassigned)
References
Details
(Keywords: html5)
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•14 years ago
|
||
dispatchFormInput and dispatchFormChange are indeed very strange. Do you happen to
know why they were added to HTML5?
Reporter | ||
Comment 2•14 years ago
|
||
(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•14 years ago
|
||
There has been some new discussion @
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129
Reporter | ||
Updated•14 years ago
|
Reporter | ||
Comment 4•14 years ago
|
||
WONTFIX, per w3c bug.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•