Tapestry 5
  1. Tapestry 5
  2. TAP5-1855

JavaScript callback on grid inplace update

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: tapestry-core
    • Labels:

      Description

      It's no direct way to call JS function from InplaceUpdate event handler

      Not in this case:
      void onInplaceUpdateFromGrid(String zone){
      ajaxResponseRenderer.addCallback(new JavaScriptCallback() {

      public void run(JavaScriptSupport javascriptSupport)

      { javascriptSupport.addInitializerCall("updateGrid",""); }

      });
      }

      neither in this case:
      void onInplaceUpdateFromGrid(String zone)

      { javascriptSupport.addScript("Tapestry.Initializer.updateGrid()"); }

      function's call don't posted in update zone AJAX response to client.
      It should be to reinitialize styles in updated part.

        Activity

        Hide
        Jochen Kemnade added a comment -

        We assume this is no longer relevant and therefore close it.
        If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

        Show
        Jochen Kemnade added a comment - We assume this is no longer relevant and therefore close it. If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
        Hide
        Jochen Kemnade added a comment -

        This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
        If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

        Show
        Jochen Kemnade added a comment - This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant. If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

          People

          • Assignee:
            Unassigned
            Reporter:
            Mihail Slobodyanuk
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development