ICEfaces
  1. ICEfaces
  2. ICE-6420

tree code active when rendered=false

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.1
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 2
    • Assignee Priority:
      P1
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      If the data model includes nodes that should not currently be rendered, then instead of using that master data model, build a cloned and pruned data model, and have the tree use that.
      Show
      If the data model includes nodes that should not currently be rendered, then instead of using that master data model, build a cloned and pruned data model, and have the tree use that.

      Description

      http://www.icefaces.org/JForum/posts/list/18300.page
      http://www.icefaces.org/JForum/posts/list/17692.page
      http://www.icefaces.org/JForum/posts/list/18306.page
      http://jira.icefaces.org/browse/ICE-3983?focusedCommentId=29886&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_29886


      From the forums threads, and JIRA comment, it appears that several code paths in Tree and TreeNode are running, when Tree.rendered=false or TreeNode.rendered=false, leading to garbled display, and invalid application state.

        Activity

        Mark Collette created issue -
        Mark Collette made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 2.0.1 [ 10255 ]
        Ken Fyten made changes -
        Salesforce Case []
        Assignee Priority P2
        Assignee Arturo Zambrano [ artzambrano ]
        Ken Fyten made changes -
        Assignee Arturo Zambrano [ artzambrano ] Mark Collette [ mark.collette ]
        Ken Fyten made changes -
        Salesforce Case []
        Assignee Priority P2 P1
        Mark Collette made changes -
        Mark Collette made changes -
        Workaround Description If the data model includes nodes that should not currently be rendered, then instead of using that master data model, build a cloned and pruned data model, and have the tree use that.
        Workaround Exists [Yes]
        Salesforce Case []
        Mark Collette made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Won't Fix [ 2 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: