[
https://issues.apache.org/jira/browse/WICKET-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5383.
-------------------------------------
Resolution: Duplicate
> AutoCompleteTextField not positionned correctly
> -----------------------------------------------
>
> Key: WICKET-5383
> URL: https://issues.apache.org/jira/browse/WICKET-5383
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 6.11.0
> Reporter: Antoine Dupuis
> Priority: Minor
>
> Hello,
> I recently upgraded to wicket 6.11.0 because I needed WICKET-5315 to fix a
> problem with AjaxFormComponentUpdatingBehavior not being properly triggered
> on an AutoCompleteTextField redrawn via ajax.
> However, it seems another fix released in this version, WICKET-5343, is now
> interfering with the position of the choices list : they are now located a
> few hundred pixels away from their input.
> This behavior is consistent across all major browsers.
> I took a quick look at the JavaScript code of this component to check if I
> could fix this, but honestly I found it far too complex to be edited and
> maintained without side effects. I had to revert the 6.11.0 code back to the
> 6.10.0 version to get the input working properly again.
> The main problem I see here is that this component is so complex that any
> change in its code is likely to break it for a few people.
> How do you propose to address this issue ?
> Shouldn't such JavaScript matters be delegated to 3rd party libraries, such
> as jQuery UI position() ?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
