Wicket
  1. Wicket
  2. WICKET-5082

Ajax update renders parent/child JS in different order than initial Page render

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.6.0
    • Fix Version/s: 6.7.0
    • Component/s: None
    • Labels:
      None

      Description

      See attached quickstart. On initial page load, the child Javascripts are rendered and executed first, followed by the parent's JS - in this case a Datatables.net JS. Everything works fine.

      However, if you click on a link in the DefaultDataTable, we trigger a DDT refresh via Ajax, and then you can see that the parent's JS is executed first, before the child JS - this causes a problem since the parent JS modifies the visible rows in the table and Wicket can no longer find some of the child rows.

      I expected the order of JS contributions to be the same for initial page render and any Ajax updates.

      1. wicket-5082.patch
        4 kB
        Sven Meier
      2. Change_order_of_Ajax_child_visitation.patch
        4 kB
        Nick Pratt
      3. quickstart.tar.gz
        95 kB
        Nick Pratt

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Sven Meier
            Reporter:
            Nick Pratt
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development