ICEfaces
  1. ICEfaces
  2. ICE-1335

icefaces-extras.js not loaded on subsequent page renders

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6DR#2
    • Fix Version/s: 1.6DR#2, 1.6
    • Component/s: Bridge
    • Labels:
      None
    • Environment:
      JBoss 4.0.4, Firefox 1.5
    • Workaround Exists:
      Yes
    • Workaround Description:
      Put a UIComponent that uses effects in your UIComponent tree, outside of dynamic ui:includes, to force it to have the SCRIPT tag from the get-go.

      Description

      If you use the Facelets dynamic ui:include version of component-showcase, and click on the Effects node of the tree, then the effects won't work.

      Basically, the first page view of component-showcase does not include any UIComponents that require the icefaces-extras.js file, so it's rendered without that. Then, when the Effects page renders, it tells the framework to include that SCRIPT tag for icefaces-extras.js. But, when the DOM diff tries to work up the tree to find a parent node with an ID, so it can send that change to the browser, it can't since the HEAD tag has no ID. Plus, even if the HEAD tag did have an ID, updating it effectively removes the HEAD from the browser DOM, and messes everything up.

      So, it would be nice to find some way of only referencing the ~200KB icefaces-extras.js when effects are in use, but we might have to just force its usage for now, so that dynamic ui:include will work properly.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Mark Collette
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: