[jira] [Updated] (TRINIDAD-2509) For date pattern=yyyy:DDD HH:mm:ss, validation error is thrown even when the date is selected from popup and is correct
[ https://issues.apache.org/jira/browse/TRINIDAD-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2509: - Status: Patch Available (was: Open) > For date pattern=:DDD HH:mm:ss, validation error is thrown even when the > date is selected from popup and is correct > --- > > Key: TRINIDAD-2509 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2509 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.1.0-core > Environment: Issue occurs on all platforms >Reporter: Anshu Jain > Attachments: TRINIDAD-2509.patch > > > For a date component, the pattern is set to ":DDD HH:mm:ss". > On opening the calendar popup and selecting a date, a validation error is > thrown: > Error: The date or time entered is not valid. > The date in the date filed is in correct format at this time. But, the > validation error is incorrectly thrown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRINIDAD-2509) For date pattern=yyyy:DDD HH:mm:ss, validation error is thrown even when the date is selected from popup and is correct
Anshu Jain created TRINIDAD-2509: Summary: For date pattern=:DDD HH:mm:ss, validation error is thrown even when the date is selected from popup and is correct Key: TRINIDAD-2509 URL: https://issues.apache.org/jira/browse/TRINIDAD-2509 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.1.0-core Environment: Issue occurs on all platforms Reporter: Anshu Jain For a date component, the pattern is set to ":DDD HH:mm:ss". On opening the calendar popup and selecting a date, a validation error is thrown: Error: The date or time entered is not valid. The date in the date filed is in correct format at this time. But, the validation error is incorrectly thrown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRINIDAD-2360) Size of the pop-up window does not honor the width and height parameters provided in IE
[ https://issues.apache.org/jira/browse/TRINIDAD-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2360: - Status: Patch Available (was: Open) > Size of the pop-up window does not honor the width and height parameters > provided in IE > --- > > Key: TRINIDAD-2360 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2360 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.0.0-core, 2.0.1-core, 2.1.0-core > Environment: The issue occurs only in Internet Explorer. >Reporter: Anshu Jain >Priority: Minor > Attachments: TRINIDAD-2360.patch > > > If the width and height of a pop-up window is passed on as parameters, the > pop-up on opening is not of the provided size. The width is slightly more and > the height is reduced from the provided parameters. This behaviors occurs > only in IE. For other browsers like Chrome and Firefox, the popup is of > correct size as passed through the parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2360) Size of the pop-up window does not honor the width and height parameters provided in IE
Anshu Jain created TRINIDAD-2360: Summary: Size of the pop-up window does not honor the width and height parameters provided in IE Key: TRINIDAD-2360 URL: https://issues.apache.org/jira/browse/TRINIDAD-2360 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.1-core, 2.0.0-core, 2.1.0-core Environment: The issue occurs only in Internet Explorer. Reporter: Anshu Jain Priority: Minor If the width and height of a pop-up window is passed on as parameters, the pop-up on opening is not of the provided size. The width is slightly more and the height is reduced from the provided parameters. This behaviors occurs only in IE. For other browsers like Chrome and Firefox, the popup is of correct size as passed through the parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2355) The error message displayed for a large file uploaded is not browser locale dependent
[ https://issues.apache.org/jira/browse/TRINIDAD-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2355: - Status: Patch Available (was: Open) > The error message displayed for a large file uploaded is not browser locale > dependent > - > > Key: TRINIDAD-2355 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2355 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.0.0-core, 2.0.1-core, 2.1.0-core > Environment: The bug occurs across environments. >Reporter: Anshu Jain > Attachments: TRINIDAD-2355.patch > > > When using inputFile component to upload a too large file, the error message > "The file could not be uploaded because it is too large" popups up. But this > message is rendered in the default locale set in the server and not in the > browser locale. > The message should appear according to the browser locale. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2355) The error message displayed for a large file uploaded is not browser locale dependent
Anshu Jain created TRINIDAD-2355: Summary: The error message displayed for a large file uploaded is not browser locale dependent Key: TRINIDAD-2355 URL: https://issues.apache.org/jira/browse/TRINIDAD-2355 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.1-core, 2.0.0-core Environment: The bug occurs across environments. Reporter: Anshu Jain When using inputFile component to upload a too large file, the error message "The file could not be uploaded because it is too large" popups up. But this message is rendered in the default locale set in the server and not in the browser locale. The message should appear according to the browser locale. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2333) When date format is set as Day of Year, only a text "(Day of Year)" is returned
[ https://issues.apache.org/jira/browse/TRINIDAD-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2333: - Status: Patch Available (was: Open) > When date format is set as Day of Year, only a text "(Day of Year)" is > returned > --- > > Key: TRINIDAD-2333 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2333 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.0.0-core, 2.0.1-core > Environment: Issue occurs on all platforms >Reporter: Anshu Jain > Attachments: TRINIDAD-2333.patch > > > The Trinidad client-side pattern output formatting support for > convertDateTime does not have logic for the 'D' character (day in year). If > the date format is set to Day of Year for a Date component, whatever date is > selected, it is replaced by the text "(Day of Year)". Actual day of year is > not displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2333) When date format is set as Day of Year, only a text "(Day of Year)" is returned
[ https://issues.apache.org/jira/browse/TRINIDAD-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2333: - Status: Open (was: Patch Available) > When date format is set as Day of Year, only a text "(Day of Year)" is > returned > --- > > Key: TRINIDAD-2333 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2333 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.0.0-core, 2.0.1-core > Environment: Issue occurs on all platforms >Reporter: Anshu Jain > Attachments: TRINIDAD-2333.patch > > > The Trinidad client-side pattern output formatting support for > convertDateTime does not have logic for the 'D' character (day in year). If > the date format is set to Day of Year for a Date component, whatever date is > selected, it is replaced by the text "(Day of Year)". Actual day of year is > not displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2333) When date format is set as Day of Year, only a text "(Day of Year)" is returned
[ https://issues.apache.org/jira/browse/TRINIDAD-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshu Jain updated TRINIDAD-2333: - Status: Patch Available (was: Open) > When date format is set as Day of Year, only a text "(Day of Year)" is > returned > --- > > Key: TRINIDAD-2333 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2333 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 2.0.0-core, 2.0.1-core > Environment: Issue occurs on all platforms >Reporter: Anshu Jain > > The Trinidad client-side pattern output formatting support for > convertDateTime does not have logic for the 'D' character (day in year). If > the date format is set to Day of Year for a Date component, whatever date is > selected, it is replaced by the text "(Day of Year)". Actual day of year is > not displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2333) When date format is set as Day of Year, only a text "(Day of Year)" is returned
Anshu Jain created TRINIDAD-2333: Summary: When date format is set as Day of Year, only a text "(Day of Year)" is returned Key: TRINIDAD-2333 URL: https://issues.apache.org/jira/browse/TRINIDAD-2333 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.1-core, 2.0.0-core Environment: Issue occurs on all platforms Reporter: Anshu Jain The Trinidad client-side pattern output formatting support for convertDateTime does not have logic for the 'D' character (day in year). If the date format is set to Day of Year for a Date component, whatever date is selected, it is replaced by the text "(Day of Year)". Actual day of year is not displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
[
https://issues.apache.org/jira/browse/TRINIDAD-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshu Jain updated TRINIDAD-2282:
-
Status: Patch Available (was: Open)
> 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
[jira] [Comment Edited] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
[
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
[jira] [Updated] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
[
https://issues.apache.org/jira/browse/TRINIDAD-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshu Jain updated TRINIDAD-2282:
-
Status: Open (was: Patch Available)
> 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
>
> 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
[jira] [Updated] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
[
https://issues.apache.org/jira/browse/TRINIDAD-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshu Jain updated TRINIDAD-2282:
-
Status: Patch Available (was: Open)
> 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
>
> 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
[jira] [Created] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
Anshu Jain created TRINIDAD-2282:
Summary: 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
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
