Tapestry 5
  1. Tapestry 5
  2. TAP5-1264

Ordering of MarkupRenderer (and PartialMarkupRender) filters can cause bad interraction between ClientBehaviorSupport and Heartbeat

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0, 5.2.1
    • Fix Version/s: 5.2.1
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Activity

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Hide
        Howard M. Lewis Ship added a comment -

        I'm hoping this fix addresses Andy's original problem. If not, please re-open.

        Show
        Howard M. Lewis Ship added a comment - I'm hoping this fix addresses Andy's original problem. If not, please re-open.
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.2.1 [ 12315230 ]
        Resolution Fixed [ 1 ]
        Hide
        Andy Blower added a comment -

        This seems to fix the issue.

        Show
        Andy Blower added a comment - This seems to fix the issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development