ICEfaces
  1. ICEfaces
  2. ICE-6282

Order of portlet loading/rendering affects component behaviour

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.2-EE-GA_P01
    • Fix Version/s: 1.8.2-EE-GA_P02
    • Labels:
      None
    • Environment:
      ICEfaces 1 portal portlet Liferay 5 and 6

      Description

      Certain component showcase examples don't function as designed if they are not loaded/rendered in a certain order. Specifically, a certain subset of components appear to only function correctly if they are loaded/rendered last on a portal page. This includes the case if they are the only portlet on the page. If they are on a page with other portlets and they are not the the last one rendered, they exhibit the following issues:

      - Auto Complete: the autocomplete menu does not drop down
      - Drag N Drop: the first drag/drop operation doesn't function properly
      - Panel Positioned: will not allow any drag/drop operation (or the first one may work but further attempts will not)
      - Rich Text: has a number of different symptoms which all seem to be related to this error (from FireBug)

      [window.twbO#8] failed to insert element: <script id="twbOVQVPOy0I223ga8UZ1Q:8:dynamic-code" type="text/javascript">...</script> TypeError: Ice.FCKeditorUtility is undefined { message="Ice.FCKeditorUtility is undefined", more...}

      If the Rich Text component is not the last one rendered, the above problem will manifest itself and lead to other problems (like not being able to change toolbar modes and not saving properly).

        Activity

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Deryk Sinotte
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: