Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-5585

Wicket Extension Automplete does not work well with JavaScriptFilteredIntoFooterHeaderResponse

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 6.15.0
    • Fix Version/s: 6.16.0, 7.0.0-M2
    • Component/s: wicket-extensions
    • Labels:
      None
    • Environment:
      Ubuntu Java 7

      Description

      When using JavaScriptFilteredIntoFooterHeaderResponse to render JS items at the bottom of the document body, this does not affect OnDomReadyHeaderItems. Wicket Extensions Autocomplete Textfield relies on such a OnDomReadyHeaderItem. As a consequence, when using both, the first item in the document HEAD calls Wicket.AutoComplete before the respective wicket js file has been loaded, breaking the Autocomplete Textfield.

      Additionally JavaScriptFilteredIntoFooterHeaderResponse is final, so it cannot be trivially patched. our current workaround was to copy & paste JavaScriptFilteredIntoFooterHeaderResponse using a custom filter.

      Not sure how best to fix this.

        Attachments

        1. wicket-autocomplete.tar.gz
          19 kB
          Thibault Kruse
        2. mantapgan.jpg
          6 kB
          Hendy Irawan

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                mgrigorov Martin Tzvetanov Grigorov
                Reporter:
                tkruse Thibault Kruse
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: