[
https://issues.apache.org/jira/browse/WICKET-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640393#comment-13640393
]
Andrei Badea commented on WICKET-5154:
--------------------------------------
I can provide a patch for the clientTop/clientLeft solution if wanted. Since
this has the potential of breaking other users due to browser bugs, should
there be a new setting for it in AutoCompleteSettings?
> Positioning of autocomplete popup does not take into account borders
> --------------------------------------------------------------------
>
> Key: WICKET-5154
> URL: https://issues.apache.org/jira/browse/WICKET-5154
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 6.6.0
> Reporter: Andrei Badea
> Attachments: test.html
>
>
> In wicket-autocomplete.js function getPosition() is used to compute the
> position of the input that the autocomplete is attached to. It uses the
> offsetTop and offsetLeft DOM properties, which does not take the borders into
> account. This causes the popup to be misplaced in all three browsers I have
> tested: IE9, Firefox 16 and Chrome 22.
> A possible solution is to take the (non-standard) clientTop and clientLeft
> properties into account, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
