Hey Matthias, I'll gladly report it, but who should I report it to?
Tomahawk to suggest not to require a naming container based form? Or Trinidad to suggest making one such environment available from tr:form? As for Adam's response, thank you for your suggestion. The solution you proposed is valid and I'm keeping it: using two separate forms, one h:form for jscookmenu and one tr:form for other purposes where I require the extended functionality. --Francisco On 6/22/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Francisco, I think it (jscookm.) requires a naming container based form (the jsCookMenu), so please file a bug against it. -M On 6/22/07, Adam Winer <[EMAIL PROTECTED]> wrote: > You can use h:form with Trinidad, FWIW, so if > jsCookMenu isn't working you could switch that way. > > -- Adam > > > On 6/22/07, Francisco Passos <[EMAIL PROTECTED]> wrote: > > No errors, neither on the client, nor on the server... > > > > The page we're on just refreshes, like when returning a null navigation > > string from an action. > > > > > > On 6/22/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > do you get any errors ? > > > on the client (javascript) > > > or on the server ? > > > > > > the difference between h:form and tr:form is, for instance, that > > > tr:form isn't a namingContainer. > > > > > > -M > > > > > > On 6/22/07, Francisco Passos < [EMAIL PROTECTED]> wrote: > > > > Good morning. > > > > > > > > It seems jsCookMenu entries do not navigate properly when placed inside > > a > > > > tr:form, whereas if we use a h:form if works fine. > > > > > > > > Is this a bug? Is there a known workaround? > > > > > > > > --Francisco > > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > further stuff: > > > blog: http://matthiaswessendorf.wordpress.com/ > > > mail: matzew-at-apache-dot-org > > > > > > > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
