Bug 43463 - Spin-button behavior improvement for out-of-range values
Summary: Spin-button behavior improvement for out-of-range values
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Kent Tamura
URL: http://crbug.com/50823
Keywords:
Depends on:
Blocks: 27968
  Show dependency tree / graph
 
Reported: 2010-08-03 21:25 PDT by Kent Tamura
Modified: 2010-08-04 22:55 PDT (History)
4 users (show)

See Also:

Attachments
Patch (7.39 KB, patch)
2010-08-03 21:30 PDT, Kent Tamura 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kent Tamura 2010-08-03 21:25:57 PDT 
The original bug report, crbug.com/50823, describes the issue on type=date.  But it is common to types with spin buttons.
Comment 1 Kent Tamura 2010-08-03 21:30:44 PDT 
Created attachment 63412 [details]
Patch
Comment 2 Darin Adler 2010-08-03 23:33:14 PDT 
Comment on attachment 63412 [details]
Patch

The wording of the log messages in the eventSender version of the test are strange. They sound like instructions for running the test manually, yet they are not.

Is there any way to click an input field with a DOM event instead of eventSender? It would be better if the test did not rely on eventSender, and the DOM does offer a way to create events.
Comment 3 Kent Tamura 2010-08-04 22:53:54 PDT 
Thank you for reviewing.

(In reply to comment #2)
> (From update of attachment 63412 [details])
> The wording of the log messages in the eventSender version of the test are strange. They sound like instructions for running the test manually, yet they are not.

I updated the messages.

> Is there any way to click an input field with a DOM event instead of eventSender? It would be better if the test did not rely on eventSender, and the DOM does offer a way to create events.

I changed eventSender to document.createEvent() and initKeyboardEvent().


Landed as r64711.