[
https://issues.apache.org/jira/browse/WICKET-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000672#comment-16000672
]
ASF GitHub Bot commented on WICKET-6366:
----------------------------------------
GitHub user perhuss opened a pull request:
https://github.com/apache/wicket/pull/220
WICKET-6366: Autocomplete race condition makes page unresponsive
Fixed bug.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/perhuss/wicket wicket-7.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/wicket/pull/220.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #220
----
commit c722e0a136583fb6a05475bd4dd492e2cebe4440
Author: phuss <[email protected]>
Date: 2017-05-08T12:31:17Z
WICKET-6366: Autocomplete race condition makes page unresponsive
----
> 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)
