ICEfaces
  1. ICEfaces
  2. ICE-11520

ace:richTextEntry, timing issue with saveOnSubmit

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-3.3.0.GA_P08, EE-4.3.0.GA_P03
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      Any

      Description

      There's a timing issue with ace:richTextEntry and saveOnSubmit when submitting the form by an external component. What happens is that the value of the ace:richTextEntry component is only made available for submission when the component is blurred. So, if an external component, such as a button, triggers a form submission by an onclick event (while the ace:richTextEntry component has focus) the blur event of the ace:richTextEntry doesn't get executed before the onclick event of the other component, so what's submitted is not the latest value of the ace:richTextEntry component. This issue is clearly seen when submitting the form via a menut item. When using a simple h:commandButton, this issue usually doesn't happen, but it does happen some times. Clicking a second time on the submit button does update the value correctly.

      This JIRA is to find a better approach to prevent this issue or to adjust the delays with which events are triggered.

        Activity

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: