Re: JSCoockMenu, hidden inputs and name attribute

2007-03-27 Thread Gary VanMatre
From: [EMAIL PROTECTED] Hi In my quest for better samples and documentation, I have started creating sample Clay configurations for the variuos Tomahawk components. I have run into an issue that has made me scratch my head a bit. First there is an issue[1], [2] with the Tomahawk

SV: JSCoockMenu, hidden inputs and name attribute

2007-03-27 Thread Hermod Opstvedt
Hi See comment inline bwlow -Opprinnelig melding- Fra: Gary VanMatre [mailto:[EMAIL PROTECTED] Sendt: 27. mars 2007 17:51 Til: dev@shale.apache.org Emne: Re: JSCoockMenu, hidden inputs and name attribute From: [EMAIL PROTECTED] Hi In my quest for better samples and documentation

Re: JSCoockMenu, hidden inputs and name attribute

2007-03-27 Thread Mike Kienenberger
On 3/27/07, Gary VanMatre [EMAIL PROTECTED] wrote: I think it becomes an issue if you are using the same component by id within the same naming container. But, I think that there are several efforts to solve the problem. The Trinidad tr:form component is not a naming container. This means

JSCoockMenu, hidden inputs and name attribute

2007-03-26 Thread hermod.opstvedt
Hi In my quest for better samples and documentation, I have started creating sample Clay configurations for the variuos Tomahawk components. I have run into an issue that has made me scratch my head a bit. First there is an issue[1], [2] with the Tomahawk JSCoockMenu and the inner form.