Beehive
  1. Beehive
  2. BEEHIVE-226

expandOnServer doesn't apply expand/contract the nodes on the Client

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: V1Beta
    • Fix Version/s: V1Beta
    • Component/s: NetUI
    • Labels:
      None

      Description

      When an expandOnServer node is expanded, we recursively render the children. If one of the children is collapsed, we are currently not collapsing that node on the client. The result is that the client and the server state mismatch.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        11d 1m 1 Daryl Olander 13/Feb/05 03:28
        Resolved Resolved Closed Closed
        58d 3h 27m 1 Krista Baker 12/Apr/05 07:56
        Krista Baker made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Hide
        Krista Baker added a comment -

        Verified, expandOnServer nodes now expand and contract correctly on the client

        Show
        Krista Baker added a comment - Verified, expandOnServer nodes now expand and contract correctly on the client
        Karen Stutesman made changes -
        Assignee Karen Stutesman [ kstutesman ] Krista Baker [ kbaker ]
        Alejandro Ramirez made changes -
        Assignee Alejandro Ramirez [ alramire ] Karen Stutesman [ kstutesman ]
        Hide
        Alejandro Ramirez added a comment -

        Please verify

        Show
        Alejandro Ramirez added a comment - Please verify
        Daryl Olander made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Assignee Daryl Olander [ dolander ] Alejandro Ramirez [ alramire ]
        Hide
        Daryl Olander added a comment -

        This was actually a bigger problem than first described. The problem was that the initialization code did not run so not only did the expand/collapse no get reflected (coreWeb/richtree/expandOnServer.jsp), the expand/collapse link was not set correctly. The result was that on expansion, the node actually caused the page to post.

        A good example of this working properly is coreWeb/tree/expand/Controller.jpf

        Show
        Daryl Olander added a comment - This was actually a bigger problem than first described. The problem was that the initialization code did not run so not only did the expand/collapse no get reflected (coreWeb/richtree/expandOnServer.jsp), the expand/collapse link was not set correctly. The result was that on expansion, the node actually caused the page to post. A good example of this working properly is coreWeb/tree/expand/Controller.jpf
        Daryl Olander created issue -

          People

          • Assignee:
            Krista Baker
            Reporter:
            Daryl Olander
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development