[
https://issues.apache.org/jira/browse/WICKET-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595188#action_12595188
]
richardwilko edited comment on WICKET-1355 at 5/8/08 7:16 AM:
---
I tried this on my code, but now the autocomplete div appears behind some of
the content on my page (its not flash or anything, just normal html + css) On
firefox . Didnt have this problem with wicket 1.3.0
Edit:
the problem seems to be how the div is added to the page. In the newer version
it is like this:
wicketGet(elementId).parentNode.appendChild(choiceDiv); (line 159)
and in the older version it was like this:
document.body.appendChild(choiceDiv);
I changed it back to the old way and everything works as before.
was (Author: richardwilko):
I tried this on my code, but now the autocomplete div appears behind some
of the content on my page (its not flash or anything, just normal html + css)
On firefox . Didnt have this problem with wicket 1.3.0
> 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: Janne Hietamäki
> Fix For: 1.3.4
>
> Attachments: 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.
