[jira] Created: (WICKET-2636) Wicket enclosure cannot find wicket container children when hidden and in an extended page
Wicket enclosure cannot find wicket container children when hidden and in an extended page -- Key: WICKET-2636 URL: https://issues.apache.org/jira/browse/WICKET-2636 Project: Wicket Issue Type: Bug Affects Versions: 1.4.5, 1.4.4, 1.4.3, 1.4.2 Environment: Java 6, Linux 64bit Reporter: Richard Wilkinson When you have a wicket:enclosure, which is in a page which extends markup of another page, then it cannot find wicket:container components which are inside it, when it is hidden. wicket:extend wicket:enclosure child=child div wicket:id=div/div wicket:container wicket:id=container/wicket:container div wicket:id=child/div /wicket:enclosure /wicket:extend It gives the normal wicket component not found exception, that you get when you don't reference the wicket:id in markup. Change the wicket:container to a div (or other html element) and it works correctly. Works on 1.4.1, 1.4.2 gives a different error, 1.4.3-1.4.5 give the error described here. It only seems to happen if the page extends markup, if you place it into a page which does not extend markup it works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2636) Wicket enclosure cannot find wicket container children when hidden and in an extended page
[ https://issues.apache.org/jira/browse/WICKET-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Wilkinson updated WICKET-2636: -- Attachment: enclosure-component.zip Quickstart attached which shows the bug Wicket enclosure cannot find wicket container children when hidden and in an extended page -- Key: WICKET-2636 URL: https://issues.apache.org/jira/browse/WICKET-2636 Project: Wicket Issue Type: Bug Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5 Environment: Java 6, Linux 64bit Reporter: Richard Wilkinson Attachments: enclosure-component.zip When you have a wicket:enclosure, which is in a page which extends markup of another page, then it cannot find wicket:container components which are inside it, when it is hidden. wicket:extend wicket:enclosure child=child div wicket:id=div/div wicket:container wicket:id=container/wicket:container div wicket:id=child/div /wicket:enclosure /wicket:extend It gives the normal wicket component not found exception, that you get when you don't reference the wicket:id in markup. Change the wicket:container to a div (or other html element) and it works correctly. Works on 1.4.1, 1.4.2 gives a different error, 1.4.3-1.4.5 give the error described here. It only seems to happen if the page extends markup, if you place it into a page which does not extend markup it works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-1738) New page map suitable for use in terracotta
New page map suitable for use in terracotta --- Key: WICKET-1738 URL: https://issues.apache.org/jira/browse/WICKET-1738 Project: Wicket Issue Type: New Feature Components: wicket Environment: Java 5+ required Reporter: Richard Wilkinson Priority: Minor Following on from discussion in this thread: http://www.nabble.com/Terracotta-integration-td18168616.html A new implementation of PageStore has been created which stores the page map in the users http session so that it is easy for terracotta to distribute the page map. Pages are serialized stored as byte arrays. Also required is updating of the wicket terracotta integration module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1738) New page map suitable for use in terracotta
[ https://issues.apache.org/jira/browse/WICKET-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611568#action_12611568 ] Richard Wilkinson commented on WICKET-1738: --- Forgot to mention, also requires that org.apache.wicket.protocol.http.pagestore.AbstractPageStore$SerializedPage implements IClusterable rather than Serializable New page map suitable for use in terracotta --- Key: WICKET-1738 URL: https://issues.apache.org/jira/browse/WICKET-1738 Project: Wicket Issue Type: New Feature Components: wicket Environment: Java 5+ required Reporter: Richard Wilkinson Priority: Minor Attachments: TerracottaPageStore.java Following on from discussion in this thread: http://www.nabble.com/Terracotta-integration-td18168616.html A new implementation of PageStore has been created which stores the page map in the users http session so that it is easy for terracotta to distribute the page map. Pages are serialized stored as byte arrays. Also required is updating of the wicket terracotta integration module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1738) New page map suitable for use in terracotta
[ https://issues.apache.org/jira/browse/WICKET-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611794#action_12611794 ] Richard Wilkinson commented on WICKET-1738: --- It could probably be added as part of the terracotta module, but there isn't any terracotta specific stuff in it. Its only an implementation of IPageStore which uses the HttpSession to keep pages. It could have other uses apart from terracotta and does work without terracotta. The main reason I thought it would be best in the wicket source is that then it is more likely to be kept in sync with any future changes to how the PageStore is used. New page map suitable for use in terracotta --- Key: WICKET-1738 URL: https://issues.apache.org/jira/browse/WICKET-1738 Project: Wicket Issue Type: New Feature Components: wicket Environment: Java 5+ required Reporter: Richard Wilkinson Priority: Minor Attachments: TerracottaPageStore.java Following on from discussion in this thread: http://www.nabble.com/Terracotta-integration-td18168616.html A new implementation of PageStore has been created which stores the page map in the users http session so that it is easy for terracotta to distribute the page map. Pages are serialized stored as byte arrays. Also required is updating of the wicket terracotta integration module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WICKET-1355) Autocomplete window has wrong position in scrolled context
[ https://issues.apache.org/jira/browse/WICKET-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595188#action_12595188 ] richardwilko edited comment on WICKET-1355 at 5/8/08 4:08 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 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). 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.
[jira] Issue Comment Edited: (WICKET-1355) Autocomplete window has wrong position in scrolled context
[ https://issues.apache.org/jira/browse/WICKET-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
