[ https://issues.apache.org/jira/browse/TAP5-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906493#action_12906493 ]
Andy Blower commented on TAP5-1264: ----------------------------------- This seems to fix the issue. > Ordering of MarkupRenderer (and PartialMarkupRender) filters can cause bad > interraction between ClientBehaviorSupport and Heartbeat > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TAP5-1264 > URL: https://issues.apache.org/jira/browse/TAP5-1264 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core > Affects Versions: 5.2.0, 5.2.1 > Reporter: Howard M. Lewis Ship > Assignee: Howard M. Lewis Ship > Fix For: 5.2.1 > > > As per discussion: http://tapestry.markmail.org/thread/sl6scyb4ccnulmgm > Heartbeat should probably be near the end of the list of filters, otherwise > prior filters (which put objects into the Environment scope) may have removed > those objects from scope. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.