[
https://issues.apache.org/jira/browse/WICKET-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785895#action_12785895
]
Erik van Oosten commented on WICKET-1355:
-----------------------------------------
One disadvantage of positioning the div as sibling of the textfield is that the
dropdown div will never be able to extend the area of the first parent with
position absolute. I.e. you need to make sure that there is enough room below
the textfield within the parent (make sure some more input fields follow, or
just add some empty space). This will happen with modal windows, but this will
not be a problem at all when you have no such parent.
This disadvantage outweights the disadvantage of having no visible dropdown div
at all.
> Autocomplete window has wrong position in scrolled context
> ----------------------------------------------------------
>
> Key: WICKET-1355
> URL: https://issues.apache.org/jira/browse/WICKET-1355
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.1
> Reporter: Erik van Oosten
> Assignee: Igor Vaynberg
> Attachments: wicket-1355-wicket-1.3.x-autocomplete.patch,
> wicket-1355-wicket-1.4.x-autocomplete.patch, wicket-autocomplete.js
>
>
> When the autocompleted field is located in a scrolled div, the drop-down
> window is positioned too far down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
