[jira] Commented: (TOMAHAWK-922) JSF-1.2: JspTilesViewHandlerImpl

[ https://issues.apache.org/jira/browse/TOMAHAWK-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605743#action_12605743 ] Neal Haggard commented on TOMAHAWK-922: --- We similarly are trying to move from MyFac

[jira] Commented: (MYFACES-701) Allow custom theme.js file without duplicating jscookmenu.js

[ http://issues.apache.org/jira/browse/MYFACES-701?page=comments#action_12356417 ] Neal Haggard commented on MYFACES-701: -- As I stated in my fix, it would be nice if this was a possibility. While having three separate variables allows much flexibilit

[jira] Commented: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=comments#action_12355632 ] Neal Haggard commented on MYFACES-737: -- Also, adding the themeName to the javascript location for the theme specific resources allows us to mirror the MyFaces setup for

[jira] Updated: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=all ] Neal Haggard updated MYFACES-737: - Attachment: jscookFormPatchV5.txt Version 5 makes the changes to the Trunk, instead of branch 1_1_1. Note that I still had to add the name of the theme ont

[jira] Commented: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=comments#action_12355621 ] Neal Haggard commented on MYFACES-737: -- I pulled from Branches/1_1_1. Should I be using Trunk instead? > JSCookMenu can't be used as a child of a form, and AddResource

[jira] Commented: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=comments#action_12332722 ] Neal Haggard commented on MYFACES-737: -- Note the version 4 patch superceeds version 3, you can ignore v3 now. > JSCookMenu can't be used as a child of a form, and AddRe

[jira] Updated: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=all ] Neal Haggard updated MYFACES-737: - Attachment: jscookFormPatchV4.txt Ok, so on further investigation, if you have more than one custom theme on a page, the second and subsequent themes don't

[jira] Updated: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

[ http://issues.apache.org/jira/browse/MYFACES-737?page=all ] Neal Haggard updated MYFACES-737: - Attachment: jscookFormPatchV3.txt Here's the patch, per my last post. > JSCookMenu can't be used as a child of a form, and AddResources code for > custom t

[jira] Created: (MYFACES-737) JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete

JSCookMenu can't be used as a child of a form, and AddResources code for custom themes is incomplete Key: MYFACES-737 URL: http://issues.apache.org/jira/browse/MYFACES-737 P

[jira] Updated: (MYFACES-27) JSCookmenu cannot be used for storing data

[ http://issues.apache.org/jira/browse/MYFACES-27?page=all ] Neal Haggard updated MYFACES-27: Attachment: jscookFormPatch.txt I've attached a patch which will walk up the parent of the JSCookMenu Navigation Item and look for the first UIForm component i

[jira] Commented: (MYFACES-345) x:navigationMenuItem should have "target" attribute and can include f:param in it's body

[ http://issues.apache.org/jira/browse/MYFACES-345?page=comments#action_12319614 ] Neal Haggard commented on MYFACES-345: -- Our development team has run into this issue as well. So, I'm going to explain our request, and hope it fulfills the original p

[jira] Updated: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=all ] Neal Haggard updated MYFACES-243: - Attachment: patch2.txt 2nd patch changes one line in the decode method. We were comparing the clientId from the action against the id of the component. Ch

[jira] Commented: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=comments#action_65709 ] Neal Haggard commented on MYFACES-243: -- Yes, the patch solves the problem. > ClientId not used, so JSCookMenu fires multiple actions in tables > --

[jira] Updated: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

[ http://issues.apache.org/jira/browse/MYFACES-243?page=all ] Neal Haggard updated MYFACES-243: - Attachment: patch.txt Here's my patch for HtmlJSCookMenuRenderer.java > ClientId not used, so JSCookMenu fires multiple actions in tables >

[jira] Created: (MYFACES-243) ClientId not used, so JSCookMenu fires multiple actions in tables

ClientId not used, so JSCookMenu fires multiple actions in tables - Key: MYFACES-243 URL: http://issues.apache.org/jira/browse/MYFACES-243 Project: MyFaces Type: Bug Versions: 1.0.9 beta Repo