You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jan Stövesand (JIRA)" <de...@myfaces.apache.org> on 2007/11/15 09:24:43 UTC
[jira] Created: (TOMAHAWK-1149) panelNavigation2 seems incopatible
with Trinidad
panelNavigation2 seems incopatible with Trinidad
------------------------------------------------
Key: TOMAHAWK-1149
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1149
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Panel Navigation2
Affects Versions: 1.1.6
Reporter: Jan Stövesand
When I enable the trinidad renderer in the face-config.xml the menu doesn't work anymore. I get a javascript error
Error: clear_menu_5Fform is not defined
Following is an example of a panelNavigation that works fine, as long as I don't use Trinidad:
<h:form id="menu_form" styleClass="naked">
<t:panelNavigation2 id="pn2" styleClass="nav1" layout="list" itemClass="mypage" activeItemClass="selected" openItemClass="selected">
<t:commandNavigation2 value="index" action="index">
<t:outputText value="Home" />
</t:commandNavigation2>
</t:panelNavigation2>
</h:form>
When I use Trinidad I get Javascript errors when clicking on the navigation links and nothing else happens, i.e. no navigation or changing pages.
When I look in the sourcecode of the generated page the javascript section is indeed missing. When I disable the trinidad renderer again (removing the entry in the application section in the faces-config.xml) the javascript appears in the source of the page again. Somehow the trinidad renderer eliminates the javascript inline sections from the output.
Tested with Tomahawk 1.1.6 and Trinidad 1.0.3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TOMAHAWK-1149) panelNavigation2 seems
incompatible with Trinidad
Posted by "Jan Stövesand (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TOMAHAWK-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543213 ]
stoeve edited comment on TOMAHAWK-1149 at 11/16/07 3:13 PM:
-------------------------------------------------------------------
I setup a new server and was not able to reproduce it with Trinidad 1.0.4
I will close this issue.
was (Author: stoeve):
I tried Tomahawk 1.1.7-SNAPSHOT and Trinidad 1.0.4 and the error still persists. I am not using Facelets.
Anybody else who uses Tomahawk and Trinidad without Facelets?
> panelNavigation2 seems incompatible with Trinidad
> -------------------------------------------------
>
> Key: TOMAHAWK-1149
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1149
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Panel Navigation2
> Affects Versions: 1.1.6
> Reporter: Jan Stövesand
> Fix For: 1.1.6
>
>
> When I enable the trinidad renderer in the face-config.xml the menu doesn't work anymore. I get a javascript error
> Error: clear_menu_5Fform is not defined
> Following is an example of a panelNavigation that works fine, as long as I don't use Trinidad:
> <h:form id="menu_form" styleClass="naked">
> <t:panelNavigation2 id="pn2" styleClass="nav1" layout="list" itemClass="mypage" activeItemClass="selected" openItemClass="selected">
> <t:commandNavigation2 value="index" action="index">
> <t:outputText value="Home" />
> </t:commandNavigation2>
> </t:panelNavigation2>
> </h:form>
> When I use Trinidad I get Javascript errors when clicking on the navigation links and nothing else happens, i.e. no navigation or changing pages.
> When I look in the sourcecode of the generated page the javascript section is indeed missing. When I disable the trinidad renderer again (removing the entry in the application section in the faces-config.xml) the javascript appears in the source of the page again. Somehow the trinidad renderer eliminates the javascript inline sections from the output.
> Tested with Tomahawk 1.1.6 and Trinidad 1.0.3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-1149) panelNavigation2 seems
incompatible with Trinidad
Posted by "Jan Stövesand (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TOMAHAWK-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543213 ]
Jan Stövesand commented on TOMAHAWK-1149:
-----------------------------------------
I tried Tomahawk 1.1.7-SNAPSHOT and Trinidad 1.0.4 and the error still persists. I am not using Facelets.
Anybody else who uses Tomahawk and Trinidad without Facelets?
> panelNavigation2 seems incompatible with Trinidad
> -------------------------------------------------
>
> Key: TOMAHAWK-1149
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1149
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Panel Navigation2
> Affects Versions: 1.1.6
> Reporter: Jan Stövesand
>
> When I enable the trinidad renderer in the face-config.xml the menu doesn't work anymore. I get a javascript error
> Error: clear_menu_5Fform is not defined
> Following is an example of a panelNavigation that works fine, as long as I don't use Trinidad:
> <h:form id="menu_form" styleClass="naked">
> <t:panelNavigation2 id="pn2" styleClass="nav1" layout="list" itemClass="mypage" activeItemClass="selected" openItemClass="selected">
> <t:commandNavigation2 value="index" action="index">
> <t:outputText value="Home" />
> </t:commandNavigation2>
> </t:panelNavigation2>
> </h:form>
> When I use Trinidad I get Javascript errors when clicking on the navigation links and nothing else happens, i.e. no navigation or changing pages.
> When I look in the sourcecode of the generated page the javascript section is indeed missing. When I disable the trinidad renderer again (removing the entry in the application section in the faces-config.xml) the javascript appears in the source of the page again. Somehow the trinidad renderer eliminates the javascript inline sections from the output.
> Tested with Tomahawk 1.1.6 and Trinidad 1.0.3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-1149) panelNavigation2 seems
incompatible with Trinidad
Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TOMAHAWK-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542812 ]
Andrew Robinson commented on TOMAHAWK-1149:
-------------------------------------------
I am able to use both fine with Facelets. Try Tomahawk 1.1.7-SNAPSHOT and Trinidad 1.0.3 and see if that helps
> panelNavigation2 seems incompatible with Trinidad
> -------------------------------------------------
>
> Key: TOMAHAWK-1149
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1149
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Panel Navigation2
> Affects Versions: 1.1.6
> Reporter: Jan Stövesand
>
> When I enable the trinidad renderer in the face-config.xml the menu doesn't work anymore. I get a javascript error
> Error: clear_menu_5Fform is not defined
> Following is an example of a panelNavigation that works fine, as long as I don't use Trinidad:
> <h:form id="menu_form" styleClass="naked">
> <t:panelNavigation2 id="pn2" styleClass="nav1" layout="list" itemClass="mypage" activeItemClass="selected" openItemClass="selected">
> <t:commandNavigation2 value="index" action="index">
> <t:outputText value="Home" />
> </t:commandNavigation2>
> </t:panelNavigation2>
> </h:form>
> When I use Trinidad I get Javascript errors when clicking on the navigation links and nothing else happens, i.e. no navigation or changing pages.
> When I look in the sourcecode of the generated page the javascript section is indeed missing. When I disable the trinidad renderer again (removing the entry in the application section in the faces-config.xml) the javascript appears in the source of the page again. Somehow the trinidad renderer eliminates the javascript inline sections from the output.
> Tested with Tomahawk 1.1.6 and Trinidad 1.0.3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.