[
https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190495#comment-13190495
]
Andrea Del Bene commented on WICKET-4339:
-----------------------------------------
Hi Nick,
in the code you have attached ther's no clue of WiQuery. Your unit test seems
to contains some errors, for example you refer to autocomplete with the id
"ddc" and not with "roles".
However I've find a weird behaviour of WiQuery which might a bug of this
library. If I run the autocomplete example with wiquery in the classpath, the
Wicket autocomplete won't work because jquery will be used instead of regular
JavaScript code when component is initialize (i.e.
'$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used
(i.e. 'Wicket.Event.add(window, "domready",' etc...).
See my quickstart for further details.
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
> Key: WICKET-4339
> URL: https://issues.apache.org/jira/browse/WICKET-4339
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5.3
> Reporter: Nick Pratt
> Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests. Unsure if this is a Wicket or a
> WiQuery problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
