[jira] Resolved: (WICKET-3293) Ajax form submit and third party HTML editors

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

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

Igor Vaynberg resolved WICKET-3293.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Igor Vaynberg

the only way to fix this is to write an integration between the rich editor and wicket that is ajax-aware. this problem is not unique to wicket's ajax, it affects all ajax implementations because, like martin pointed out, the rich editors mess with DOM and need to be notified prior to an ajax form submit to dump the value into the old tag. feel free to create a wicket-stuff project that integrates the editors.

> Ajax form submit and third party HTML editors
> ---------------------------------------------
>
>                 Key: WICKET-3293
>                 URL: https://issues.apache.org/jira/browse/WICKET-3293
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M3
>         Environment: Any
>            Reporter: Ivan Vasilev
>            Assignee: Igor Vaynberg
>         Attachments: quickstart.rar
>
>
> There is a form with two textarea elements in it. 
> The first textarea is converted into a CKEditor (http://ckeditor.com/) and the second one is converted into dijit.Editor (http://docs.dojocampus.org/dijit/Editor).
> There are two submit buttons - one Ajax and one non-ajax.
> When the form is submitted with page reload (non ajax) the values from the two textarea elements are correctly submitted to the server.
> However, if the form is submitted via ajax the values from the two textarea elements are not sent to the server. This can be observed in the attached quickstart.
> This issue involves third party tools, so in a sense it's not a wicket problem, but I decided to create an issue for two reasons:
> 1. There is a repeated pattern with two different editors, which (as far as I know) have nothing in common.
> 2. There is a different behavior when the form is submitted via ajax (doesn't work) and with page reload (works). 
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.