Tapestry 5
  1. Tapestry 5
  2. TAP5-1244

Tapestry components and mixins should be converted to use JavaScriptSupport, not RenderSupport

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.1
    • Fix Version/s: 5.2.1
    • Labels:
      None

      Description

      The Autocomplete mixin is an example; since it uses RenderSupport, it means lots of unwanted calls to Tapestry.init() on the client side.

      However, this may be related to another bug about JavaScriptSupport not supported client-side initializer functions that take JSONArray (rather than a String or JSONObject).

        Activity

        Hide
        Hudson added a comment -

        Integrated in tapestry-5.2-freestyle #175 (See https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/175/)
        TAP5-1244: Recode AutofocusValidationDecorator to use JavaScriptSupport, not RenderSupport
        TAP5-1244: Move autofocus() from RenderSupport to JavaScriptSupport
        TAP5-1244: Tapestry components and mixins should be converted to use JavaScriptSupport, not RenderSupport

        Show
        Hudson added a comment - Integrated in tapestry-5.2-freestyle #175 (See https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/175/ ) TAP5-1244 : Recode AutofocusValidationDecorator to use JavaScriptSupport, not RenderSupport TAP5-1244 : Move autofocus() from RenderSupport to JavaScriptSupport TAP5-1244 : Tapestry components and mixins should be converted to use JavaScriptSupport, not RenderSupport

          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