ICEfaces
  1. ICEfaces
  2. ICE-9500

Make ice.ace.instance work with all lazy init components: checkboxEntry, dateTimeEntry, buttons, etc.

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.BETA
    • Fix Version/s: 4.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ACE
    • Assignee Priority:
      P1

      Description

      With this task, the new ice.ace.instance function from ICE-8475, which will replace widgetVar, will allow for lazy initiated components to be automatically initiated by ice.ace.instance. The idea being that with something like popup panel, which is typically made visible via its widgetVar, it previously had to eagerly initialise so that the widgetVar would be available to make it visible. Now with this alternate means of getting the javascript object reference, we can detect that the object has not yet been initialised, and do so lazily only when ice.ace.instance is called.

      Our first step needs to be to take all the components that already use lazy initialise, and integrate that to work with ice.ace.instance, as the switch to lazy init had meant that one couldn't count on accessing their widgetVar.

        Issue Links

          Activity

          Hide
          Arturo Zambrano added a comment -

          The last issues reported are not caused by this fix. They became visible after the changes made for ICE-10100. More information can be found on that JIRA.

          Show
          Arturo Zambrano added a comment - The last issues reported are not caused by this fix. They became visible after the changes made for ICE-10100 . More information can be found on that JIRA.
          Hide
          Carmen Cristurean added a comment -

          Re-opening this JIRA because of the following regressions in showcase (Icefaces 4 trunk rev. 41557/all browsers):

          messages/ textEntry/ textAreaEntry (all browsers)
          > All: demos are not functional: messages are not rendered when tabbing through without text being entered; when tabbing through after typing text, the focus jumps back to the input entry at the end of the typed text (no errors seen).
          Steps:

          • type at least one character in one of the inputs.
          • press Tab - > focus is initially visible on the next input entry, but it goes back to the first input entry, at the end of the typed text.
          Show
          Carmen Cristurean added a comment - Re-opening this JIRA because of the following regressions in showcase (Icefaces 4 trunk rev. 41557/all browsers): messages/ textEntry/ textAreaEntry (all browsers) > All: demos are not functional: messages are not rendered when tabbing through without text being entered; when tabbing through after typing text, the focus jumps back to the input entry at the end of the typed text (no errors seen). Steps: type at least one character in one of the inputs. press Tab - > focus is initially visible on the next input entry, but it goes back to the first input entry, at the end of the typed text.
          Hide
          Arturo Zambrano added a comment -

          r41527: wrapped input focus function inside a timeout function, in order to allow the child components to be loaded first before applying focus to them.

          This fixes issue #1 above.

          Show
          Arturo Zambrano added a comment - r41527: wrapped input focus function inside a timeout function, in order to allow the child components to be loaded first before applying focus to them. This fixes issue #1 above.
          Hide
          Carmen Cristurean added a comment - - edited

          Issue 1) is partially resolved only, as the ace:dialog opens up now however the inputText is missing the focus (Chrome35/ rev.41525).

          Issue 2) is resolved.

          Show
          Carmen Cristurean added a comment - - edited Issue 1) is partially resolved only, as the ace:dialog opens up now however the inputText is missing the focus (Chrome35/ rev.41525). Issue 2) is resolved.
          Hide
          Arturo Zambrano added a comment -

          r41525: Committed fix to show dialog when visible=true.

          Since ace:dialog is not lazily initialized, it was necessary to add a call to the show() function when visible=true, so that the component gets initialized right away and displayed. This fixes both issues above.

          Show
          Arturo Zambrano added a comment - r41525: Committed fix to show dialog when visible=true. Since ace:dialog is not lazily initialized, it was necessary to add a call to the show() function when visible=true, so that the component gets initialized right away and displayed. This fixes both issues above.

            People

            • Assignee:
              Arturo Zambrano
              Reporter:
              Mark Collette
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: