[ 
https://issues.apache.org/jira/browse/WICKET-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853333#action_12853333
 ] 

Juergen Donnerstag commented on WICKET-2800:
--------------------------------------------

1.3.x is no longer maintained outside of security-related issues, please 
upgrade to 1.4.x 

In case the same issue appears in 1.4.x, please provide a junit test case or 
quickstart. Thanks,

> misinterpretation of commented JS-Code in an AbstractTab (with 
> AjaxTabbedPanel)
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-2800
>                 URL: https://issues.apache.org/jira/browse/WICKET-2800
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.3.7
>         Environment: Tomcat 6, Java 1.6.0_10
>            Reporter: daniel teske
>            Priority: Minor
>
> Wicket isn't able to render the selected Tab in an AjaxTabbedPanel if there 
> is a comment JS-code that is embedded in the  <wicket:head>. When I press the 
> F5-key after clicking on the tab, the selected panel gets rendered.
> The Ajax-Debug tells "object required"
> Here is the JS-code of my AbstractTab-Markup:
> <wicket:head>
>    <script language="javascript">
>       var myVar = null;
>       function myFunction(id1, id2){
>             //do something
>       }
>       /* function myCommentedFunction(id1,id2){
>              if(id1 && id2){
>                    //do something
>              }
>       }*/
> </script>
> </wicket:head>
> Would I use a normal TabbedPanel or delete the commented JS-code the tab is 
> working fine =/
> I don't hope that this is a Major-Bug of your <wicket:head>-interpretation!
> thanks a lot,
> danielt

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