[
https://issues.apache.org/jira/browse/WICKET-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438712#comment-15438712
]
Sven Meier edited comment on WICKET-6136 at 8/29/16 2:03 PM:
-------------------------------------------------------------
I'm debugging this right now, and it seems there are two problems at least:
Sometimes the mouseover-function is not called (which makes sense on a touch
device) and in the click-function the selected index is still -1 (resulting in
"cannot read property 'attributes' of undefined") - this was easy to fix.
There's another problem with the positioning of the popup, which is opened with
a offset equalling the current scroll position:
If the window is scrolled between opening of the popup and selection of an
entry, the popup is respositioned in onmouseover->render, resulting in the
click being invoked on the wrong entry (or none at all if there's no longer an
entry under the mouse).
was (Author: svenmeier):
I'm debugging this right now, and it seems there are two problems at least:
Sometimes the mouseover-function is not called (which makes sense on a touch
device) and in the click-function the selected index is still -1 (resulting in
"cannot read property 'attributes' of undefined") - this was easy to fix.
There's another problem when any scrolling appears during selection, then the
click-function isn't called at all :(.
> AutoCompleteTextField issue in Android 5.1.1
> --------------------------------------------
>
> Key: WICKET-6136
> URL: https://issues.apache.org/jira/browse/WICKET-6136
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 7.2.0, 6.22.0
> Environment: Chrome on Samsung Galaxy Note 4 running Android 5.1.1
> Reporter: Remy Kaufmann
> Assignee: Sven Meier
> Attachments: HomePage.html, quickstart (wicket 7).zip, quickstart.zip
>
>
> Quick note: we have only been able to reproduce this issue on Samsung devices
> running Android 5.1.1. The issue affects Chrome and the Samsung browser,
> whereas Firefox appears to be fine. _2016-08-15:_ customer told us that the
> AutoCompleteTextField has also begun to show the erroneous behaviour on
> Firefox now.
> We were unable to reproduce the issue on a Nexus smartphone running Android
> 6. We were also unable to reproduce the issue on a Sony device running
> Android 5.1.1.
> Reproduction steps:
> 1. Fire up the provided Quickstart.
> 2. Enter some text (e.g. "un") to summon the list of suggestions.
> 3. Tap on one of the suggested countries.
> 4. Observe that no country was selected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
