[
https://issues.apache.org/jira/browse/WICKET-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030751#comment-16030751
]
Per Huss commented on WICKET-6366:
----------------------------------
[~mgrigorov]/[~svenmeier]: Can you please have a quick look at this issue? The
problem is causing regular but intermittent failures of our automated selenium
suite. The issue should be fully reproducible with the quickstart, and you
could probably quickly tell whether the suggested fix is at the right place or
not... I would make me very happy if this fix could make the next minor
release... Thanks!
> Autocomplete race condition makes page unresponsive
> ---------------------------------------------------
>
> Key: WICKET-6366
> URL: https://issues.apache.org/jira/browse/WICKET-6366
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 7.6.0
> Environment: Reproduced both with latest Firefox (53.0.2) and latest
> Chrome (58.0.3029.96)
> Reporter: Per Huss
> Attachments: autocomplete.zip, exceptions.png
>
>
> The autocomplete field can throw a javascript exception that makes the page
> unresponsive.
> To reproduce, run attached quickstart and:
> 1. Click the text field and type "a"
> 2. Quickly click the "hide" button, and
> 3. Quickly click the text field again and type another "a", leaving the text
> field focused.
> 4. A couple of javascript exceptions will be thrown, where the first on seems
> to break the ajax functionality. Clicking "show" has no effect now.
> Attaching quickstart and screenshot of the exceptions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
