You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2008/07/23 10:37:31 UTC

[jira] Assigned: (WICKET-1035) DOM cleanup after Ajax calls

     [ https://issues.apache.org/jira/browse/WICKET-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst reassigned WICKET-1035:
----------------------------------------

    Assignee: Matej Knopp

> DOM cleanup after Ajax calls
> ----------------------------
>
>                 Key: WICKET-1035
>                 URL: https://issues.apache.org/jira/browse/WICKET-1035
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: Firefox, Internet Explorer 6-7
>            Reporter: Ben Marvell
>            Assignee: Matej Knopp
>            Priority: Critical
>         Attachments: ajaxlink.tar.bz2
>
>
> 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).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.