Bug 43463

Summary: Spin-button behavior improvement for out-of-range values
Product: WebKit Reporter: Kent Tamura <tkent>
Component: FormsAssignee: Kent Tamura <tkent>
Status: RESOLVED FIXED    
Severity: Normal CC: adele, darin, dglazkov, ojan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://crbug.com/50823
Bug Depends on:    
Bug Blocks: 27968    
Attachments:
Description Flags
Patch none

Kent Tamura
Reported 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.
Attachments
Patch (7.39 KB, patch)
2010-08-03 21:30 PDT, Kent Tamura 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Kent Tamura
Comment 1 2010-08-03 21:30:44 PDT
Created attachment 63412 [details] Patch
Darin Adler
Comment 2 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.
Kent Tamura
Comment 3 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.
Note You need to log in before you can comment on or make changes to this bug.