[ 
https://issues.apache.org/jira/browse/TRINIDAD-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405686#comment-13405686
 ] 

Anshu Jain edited comment on TRINIDAD-2282 at 7/3/12 8:30 AM:
--------------------------------------------------------------

Code fix for this bug
when minimum value is not set for a validateLength, the default value is taken 
as 0 by the server side code. As a result min=0 is sent to the client side as 
well. In this condition, server side does not set the user defined 
hintNotInRange, but sets hintMaximum.
But, in the js, a check is done for min != null and a default hintNotInRange 
message is displayed.
This fix checks if the value of min is 0 in js, in which case, hintMaximum is 
displayed.
                
      was (Author: anshujain):
    Code fix for this bug
                  
> In validateLength, a default hintRange message is displayed instead of 
> hintMaximum even when minimum value is not set
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2282
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2282
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 2.0.0-beta-2
>         Environment: JDeveloper 11.1.2.0.0
>            Reporter: Anshu Jain
>         Attachments: TrinidadBug2282.patch
>
>
> af:validateLength is used for a input text box. The maximum value is set and 
> minimum value is not set. Which means by default minimum is 0.
> The hintMaximum is set to "{0} is maximum allowed" and hintRange is set to 
> "{0} is minimum, {1} is maximum"
> When the user clicks on the the given text box, hintMaximum should be 
> displayed.
> Instead a default message: "Enter between 0 and 3 characters." is displayed. 
> hintMaximum should be displayed in this scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to