[jira] [Updated] (WICKET-4709) AutoCompleteTextField is not working in 6.0.x - available choices are not rendered after keypress.

["Robert Szmurlo (JIRA)" <ji...@apache.org>]

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

Robert Szmurlo updated WICKET-4709:
-----------------------------------

    Attachment: Zaznaczenie_039.png

Screen of AutoCompleter in wicket-examples with debugging information showing the error in Javascript part of AutoCompleter.
                
> AutoCompleteTextField is not working in 6.0.x - available choices are not rendered after keypress.
> --------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4709
>                 URL: https://issues.apache.org/jira/browse/WICKET-4709
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 6.0.0-beta3
>         Environment: http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete?1
>            Reporter: Robert Szmurlo
>         Attachments: Zaznaczenie_039.png
>
>
> It seems that AutoCompleteTextField stopped working in Wicket 6.0.
> (It is not working SNAPSHOT, but in 1.5.x it was working ok.)
> There is an error in the Javascript part of AutoCompleteTextField.
> The error can be easily observed in wicket-examples:
> http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete?0
> Description of the problem and screen from the wicket-examples:
> 1. When user enters the first key - the request is sent to the server, which starts generating response.
> 2. The browser receives the response but it seems to be ignored by the Wicket javascript, because of
>     error in Javascript of AutoCompleteTextField (shown in the screen below).
> 3. The user enters next key - the Wicket Ajax Debug Window informs that the Chanel is busy (shown in screen below).

--
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