You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2007/03/08 05:53:24 UTC

[jira] Resolved: (WICKET-325) Enable WebMarkupContainer as target for wicketSerialize

     [ https://issues.apache.org/jira/browse/WICKET-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-325.
----------------------------------

    Resolution: Fixed

same sentiment as in WICKET-324

+ we do not want to start supporting random tags because then users will request more and more and more. if you want you can write your own js for this, you are not really meant to use wicket-ajax.js functions directly.


> 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.