[
https://issues.apache.org/jira/browse/WICKET-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475723
]
Rüdiger Schulz commented on WICKET-325:
---------------------------------------
In my use case (see WICKET-324), it doesn't make sense to do an onchange on the
first component, when the second one is most probably not yet edited at all
(going by the tabindex).
> 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.
