[ https://issues.apache.org/jira/browse/WICKET-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858263#action_12858263 ]
Kent Tong commented on WICKET-2832: ----------------------------------- I've created a patch for it. It is very simple and localized. Please consider. > Output wicket attributes even in ajax response > ---------------------------------------------- > > Key: WICKET-2832 > URL: https://issues.apache.org/jira/browse/WICKET-2832 > Project: Wicket > Issue Type: Improvement > Components: wicket > Affects Versions: 1.4.7 > Reporter: Kent Tong > Assignee: Igor Vaynberg > Attachments: patch.txt > > Original Estimate: 1h > Remaining Estimate: 1h > > I am working on a special locator in selenium for Wicket generated pages. For > example, one can like wicket:id in a xpath-like locator: //myform//username, > which means locating the first element whose wicket:id is "myform" and then > locating the first element whose wicket:id is "username". > The code is working. However, due to WICKET-1174, stripWicketTags in > renderComponentTag() is now set to true as long as it is an ajax request. So, > if an element is refreshed in an ajax request, it will lose the wicket:id and > the locator won't find it. > To solve the problem, I'd suggest the splitting the concept of "strip wicket > attributes" from "strip wicket tags". This way, you can still trip the wicket > tags without affecting the wicket:id. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira