Summary: | <input> should not trim initial value to maxLength | ||
---|---|---|---|
Product: | WebKit | Reporter: | Peter Kasting <pkasting> |
Component: | Forms | Assignee: | Michelangelo De Simone <michelangelo> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | ||
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/190 | ||
Bug Depends on: | |||
Bug Blocks: | 27454 |
Description
Peter Kasting
2009-08-04 15:16:53 PDT
Note: WebKit already does the second step above, where it pastes in as much as will fit. To see this, visit the example URL, select one character of "foo", and try pasting "maxLength". You'll see the selected character replaced by "m". Peter, do you think that we should get the standard maxlength interface in this patch, as well as adjusting the "0" issue (0 is not an accepted value now)? (In reply to comment #2) > Peter, do you think that we should get the standard maxlength interface in this > patch, as well as adjusting the "0" issue (0 is not an accepted value now)? "standard maxlength interface"? Do you mean unsigned long versus long? If so, then no, I don't think we should do that on this bug. I think this bug should stick to what I filed it as being about, and other maxLength changes can go on bug 27454 or on new bugs that block that bug. |