ICEfaces
  1. ICEfaces
  2. ICE-8242

ace:dateTimeEntry - default value of labelPosition can cause unwanted conversion errors

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.1.0.BETA2
          • Fix Version/s: 3.1.0.RC1, 3.1
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            ICEfaces 3.1.0 BETA2
          • Assignee Priority:
            P1
          • Affects:
            Compatibility/Configuration
          • Workaround Exists:
            Yes
          • Workaround Description:
            Change the labelPosition attribute to a different value than inField.

            Description

            When the label attribute is set for the ace:dateTimeEntry its value is used inside the input field. This can cause a conversion error when the form is submitted as the String label is not a valid date.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arran Mccullough added a comment -

              Attached test case that shows issue.

              Steps:

              • Run welcomeICEfaces.jsf
              • Click the Submit button, conversion error is shown.
              Show
              Arran Mccullough added a comment - Attached test case that shows issue. Steps: Run welcomeICEfaces.jsf Click the Submit button, conversion error is shown.
              Hide
              Permalink
              yip.ng added a comment -

              In-field label handling relies on focus and blur events. In this simple scenario there is neither before the submit. Had to resort back to using dummy name attribute as flag to detect on server. (These added non-trivial complexities are caused by our requirement that the label could be a valid entered value.)

              Note that the framework focus management can occasionally behave inconsistently. See http://jira.icesoft.org/secure/attachment/14555/screenshot-04.png. That is not a bug in the in-field label handling.

              Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\resources\icefaces.ace\jquery\ui\jquery-ui.js
              Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\src\org\icefaces\ace\component\datetimeentry\DateTimeEntryRenderer.java
              Completed: At revision: 29494

              Show
              yip.ng added a comment - In-field label handling relies on focus and blur events. In this simple scenario there is neither before the submit. Had to resort back to using dummy name attribute as flag to detect on server. (These added non-trivial complexities are caused by our requirement that the label could be a valid entered value.) Note that the framework focus management can occasionally behave inconsistently. See http://jira.icesoft.org/secure/attachment/14555/screenshot-04.png . That is not a bug in the in-field label handling. Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\resources\icefaces.ace\jquery\ui\jquery-ui.js Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\src\org\icefaces\ace\component\datetimeentry\DateTimeEntryRenderer.java Completed: At revision: 29494

                People

                • Assignee:
                  yip.ng
                  Reporter:
                  Arran Mccullough
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: