Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Invalid
    • Affects Version/s: 1.3.0-beta3, 1.3.0-beta4, 1.3.0-rc1, 1.3.0-rc2, 1.3.0-final, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4-M1, 1.4-M2, 1.4-M3
    • Fix Version/s: None
    • Component/s: wicket
    • Labels:
      None
    • Environment:
      Firefox, Internet Explorer 6-7

      Description

      Making Ajax requests increases the size of the DOM on each subsequent request. Please see the link below for an example;

      http://www.wicket-library.com/wicket-examples/ajax/tabbed-panel.0

      Clicking "first tab" and running the following code in the location bar:

      javascript:alert(document.getElementsByTagName("*").length);

      Returns 54 however clicking "second tab" then "first tab" again returns 142. This number will keep on growing and growing as you click on different tabs (ajax requests).

      1. ajaxlink.tar.bz2
        4 kB
        Emond Papegaaij
      2. myproject.tgz
        5 kB
        Martijn Dashorst

        Activity

        Hide
        Emond Papegaaij added a comment -

        Just start it and click the 'test' link.

        Show
        Emond Papegaaij added a comment - Just start it and click the 'test' link.
        Hide
        Emond Papegaaij added a comment -

        I don't know why this bug was closed as invalid, but we are seeing this also. The attached quickstart shows the problem. I've tested it under Firefox 3, IE 7, Konqueror 3.5 and Opera 9.51, all show the same behaviour.

        Show
        Emond Papegaaij added a comment - I don't know why this bug was closed as invalid, but we are seeing this also. The attached quickstart shows the problem. I've tested it under Firefox 3, IE 7, Konqueror 3.5 and Opera 9.51, all show the same behaviour.
        Hide
        Martijn Dashorst added a comment -

        obviously having the Wicket Ajax Debugger open will increase the count of nodes, because each request is logged in a div element. I just debugged it : and testing Wicket Ajax updates without the debugger on doesn't increase the number of nodes.

        Show
        Martijn Dashorst added a comment - obviously having the Wicket Ajax Debugger open will increase the count of nodes, because each request is logged in a div element. I just debugged it : and testing Wicket Ajax updates without the debugger on doesn't increase the number of nodes.
        Hide
        Martijn Dashorst added a comment -

        quickstart project that debunks any and all claims that Wicket Ajax leaks DOM nodes

        Show
        Martijn Dashorst added a comment - quickstart project that debunks any and all claims that Wicket Ajax leaks DOM nodes

          People

          • Assignee:
            Matej Knopp
            Reporter:
            Ben Marvell
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development