[jira] [Updated] (WICKET-5585) Wicket Extension Automplete does not work well with JavaScriptFilteredIntoFooterHeaderResponse

["Hendy Irawan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hendy Irawan updated WICKET-5585:
---------------------------------

    Attachment: mantapgan.jpg

Thank you [~mgrigorov] !

!mantapgan.jpg!

Awesome... or as us Indonesians say, mantap gan!! [~rudi] :)

> Wicket Extension Automplete does not work well with JavaScriptFilteredIntoFooterHeaderResponse
> ----------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5585
>                 URL: https://issues.apache.org/jira/browse/WICKET-5585
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-extensions
>    Affects Versions: 6.15.0
>         Environment: Ubuntu Java 7
>            Reporter: Thibault Kruse
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 6.16.0, 7.0.0-M2
>
>         Attachments: mantapgan.jpg, wicket-autocomplete.tar.gz
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)