[
https://issues.apache.org/jira/browse/TAP5-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891257#action_12891257
]
Brian Heston commented on TAP5-1192:
------------------------------------
This is a nice quick one to solve and would really help a lot so I don't have
to figure out a hack until it's resolved correctly. Please take a look.
> Ajax update memory leak fix throws exception
> --------------------------------------------
>
> Key: TAP5-1192
> URL: https://issues.apache.org/jira/browse/TAP5-1192
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Brian Heston
> Priority: Critical
>
> The fix for TAP5-1147 causes an exception when it finds an element with a
> function for an attribute value under IE 8. In the purge function in
> tapestry.js starting at line 640, the count of attributes is kept in a
> variable, then the attributes are processed starting at the beginning. When
> an attribute is found where the value is a function, the attribute is removed
> and the count of attributes changes. When the loop gets to the end, an
> exception is thrown because attrs[i] is undefined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
