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

Frank Klein Koerkamp updated WICKET-2481:
-----------------------------------------

          Component/s:     (was: wicket-extensions)
                       wicket
          Description: 
/*Form tag does not get rendered on a Panel placed in an AjaxTabbedPanel within 
a ModalWindow. Form contents are rendered properly but the form tag itself does 
not. The first tab of an AjaxTabbedPanel is not affected by this issue when 
rendered for the first time. But if one navigates to the second tab and returns 
back to the first tab then the form tag no longer exist there. 

This makes any forms on a tabbed panel placed on a modal window unusable.

See attached quickstart project.*/

Why is this neccesary. Currently the Firefox is not working with it, because 
the following code in wicket-ajax.js is giving problems. 
<code>
var range = element.ownerDocument.createRange();
                        range.selectNode(element);
                        var fragment = range.createContextualFragment(text);
                        
                        element.parentNode.replaceChild(fragment, element);
</code>

if i add some jquery code it will work :

<code>
try
                {
                        $(element).replaceWith(text);
                }
                catch (e)
                {
                        var range = element.ownerDocument.createRange();
                        range.selectNode(element);
                        var fragment = range.createContextualFragment(text);
                        
                        element.parentNode.replaceChild(fragment, element);
                }  
</code>



  was:
Form tag does not get rendered on a Panel placed in an AjaxTabbedPanel within a 
ModalWindow. Form contents are rendered properly but the form tag itself does 
not. The first tab of an AjaxTabbedPanel is not affected by this issue when 
rendered for the first time. But if one navigates to the second tab and returns 
back to the first tab then the form tag no longer exist there. 

This makes any forms on a tabbed panel placed on a modal window unusable.

See attached quickstart project.

          Environment: Windows XP, Tomcat 6.0.18, JDK 16u14   (was: Windows 
Vista 64-bit, Tomcat 6.0.18, JDK 16u14 )
    Affects Version/s:     (was: 1.4.0)
                       1.4.1

> CLONE -Form tag does not get rendered on a Panel placed in a TabbedPanel 
> within a ModalWindow
> ---------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2481
>                 URL: https://issues.apache.org/jira/browse/WICKET-2481
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.1
>         Environment: Windows XP, Tomcat 6.0.18, JDK 16u14 
>            Reporter: Frank Klein Koerkamp
>            Assignee: Igor Vaynberg
>
> /*Form tag does not get rendered on a Panel placed in an AjaxTabbedPanel 
> within a ModalWindow. Form contents are rendered properly but the form tag 
> itself does not. The first tab of an AjaxTabbedPanel is not affected by this 
> issue when rendered for the first time. But if one navigates to the second 
> tab and returns back to the first tab then the form tag no longer exist 
> there. 
> This makes any forms on a tabbed panel placed on a modal window unusable.
> See attached quickstart project.*/
> Why is this neccesary. Currently the Firefox is not working with it, because 
> the following code in wicket-ajax.js is giving problems. 
> <code>
> var range = element.ownerDocument.createRange();
>                       range.selectNode(element);
>                       var fragment = range.createContextualFragment(text);
>                       
>                       element.parentNode.replaceChild(fragment, element);
> </code>
> if i add some jquery code it will work :
> <code>
> try
>               {
>                       $(element).replaceWith(text);
>               }
>               catch (e)
>               {
>                       var range = element.ownerDocument.createRange();
>                       range.selectNode(element);
>                       var fragment = range.createContextualFragment(text);
>                       
>                       element.parentNode.replaceChild(fragment, element);
>               }  
> </code>

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

Reply via email to