[
https://issues.apache.org/jira/browse/WICKET-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rüdiger Schulz updated WICKET-325:
----------------------------------
Attachment: wicket-ajax.js
Here is the diff:
285c285
< var tag = e.tagName.toLowerCase();
---
> var tag = (e.tagName ? e.tagName.toLowerCase() : "");
289a290,299
> } else if (tag == "span" || tag == "div" || tag.substring(0,7) ==
> "wicket:") {
> var childElements = e.childNodes; // TODO find'em
> var result = "";
> for (var i = 0; i < childElements.length; ++i) {
> var child = childElements[i];
> if (!child.disabled) {
> result += Wicket.Form.serializeElement(child);
> }
> }
> return result;
Shouldn't change existing calls, as I think nobody relies on this returning the
empty string.
> Enable WebMarkupContainer as target for wicketSerialize
> -------------------------------------------------------
>
> Key: WICKET-325
> URL: https://issues.apache.org/jira/browse/WICKET-325
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.2.5
> Environment: Wicket 1.2.5
> Reporter: Rüdiger Schulz
> Fix For: 1.2.6
>
> Attachments: wicket-ajax.js
>
>
> It would be nice if it's possible to call the JavaScript wicketSerialize /
> Wicket.Form.serializeElement on a span or div, and then all FormComponents
> within are serialized with Wicket.Form.serializeElement. This is useful with
> my change to AjaxFormComponentUpdatingBehavior.java when I want to update a
> Border. But this might be useful for FormComponentPanel in 1.3 as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
