You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2003/11/03 00:41:10 UTC
DO NOT REPLY [Bug 24336] New: -
Text field maxlength generated by DatePicker is too small for some DateFormats
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24336>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24336
Text field maxlength generated by DatePicker is too small for some DateFormats
Summary: Text field maxlength generated by DatePicker is too
small for some DateFormats
Product: Tapestry
Version: 3.0
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Framework
AssignedTo: tapestry-dev@jakarta.apache.org
ReportedBy: pmf8@columbia.edu
In Tapestry v3.0-beta-3:
If the DatePicker component is specified with a format property that displays
the entire month (i.e. not abbreviated), e.g.
<input jwcid="@DatePicker" value="ognl:myDate" format="MMMM dd, yyyy"/>
the value parameter may bind to an incorrect date value during the rewind cycle.
For the example, the DatePicker component generates an HTML text field with a
maxlength="15". If a date is selected such as "November 03, 2003", the value as
stored in the text field will subsequently get truncated to this: "November 03,
20". During the rewind cycle, the binding of myDate will be incorrect.
Specifically, new SimpleDateFormat("MMMM dd, yyyy").parse("November 03, 20")
will return a java.util.Date with the year as "0020" instead of "2003".
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org