Closed
Bug 851780
Opened 12 years ago
Closed 12 years ago
Create a test_input_event.html test
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: jwatt, Assigned: mounir)
Details
Attachments
(1 file, 2 obsolete files)
12.24 KB,
patch
|
Details | Diff | Splinter Review |
In bug 851090 I added 'input' event tests to test_change_event.html for <input type=range> because we don't seem to have 'input' event tests elsewhere, and because it seems to make sense to test 'input' and 'change' events together. We should either renaming test_change_event.html to test_change_and_input_events.html, or else split out the 'input' event tests into a separate file.
I prefer the former solution, and then going forwards we can add more 'input' tests to the file for other types.
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
Summary: Consider renaming test_change_event.html to test_change_and_input_events.html, or split out 'input' event tests → Create a test_input_event.html test
Assignee | ||
Comment 2•12 years ago
|
||
Better if I remove the input event checks from test_change_event.html.
Attachment #730184 -
Attachment is obsolete: true
Attachment #730184 -
Flags: review?(jwatt)
Attachment #730187 -
Flags: review?(jwatt)
Reporter | ||
Updated•12 years ago
|
Attachment #730187 -
Flags: review?(jwatt) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Attachment #730187 -
Attachment is obsolete: true
Attachment #730215 -
Flags: checkin?
Assignee | ||
Comment 4•12 years ago
|
||
m-i is currently closed so marking as checkin-needed.
Keywords: checkin-needed
Updated•12 years ago
|
Attachment #730215 -
Flags: checkin?
Comment 5•12 years ago
|
||
Flags: in-testsuite+
Keywords: checkin-needed
Comment 6•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•