Just verified again with a simple form like this one:
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/Radio.html
=tml=
h2Selected type: ${type}/h2
t:zone t:id=formZone
t:form t:zone=^ t:id=radioForm
t:label for=type /:
t:radiogroup t:id=type
t:radio
JIRA is here: https://issues.apache.org/jira/browse/TAP5-2231
On Fri, Nov 22, 2013 at 9:10 AM, Magnus Kvalheim mag...@kvalheim.eu wrote:
Just verified again with a simple form like this one:
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/Radio.html
=tml=
So, was looking into fixing this myself as a temporary workaround.
I think the fix is quite clean, and of interest for others in similar
situation, so I'll briefly post it.
--
What I wanted to do was to make a modified version of forms.coffee and
contribute/override that somehow.
The
Why not submit a patch, now that you've spent the time figuring it out?
On Fri, Nov 22, 2013 at 12:07 PM, Magnus Kvalheim mag...@kvalheim.euwrote:
So, was looking into fixing this myself as a temporary workaround.
I think the fix is quite clean, and of interest for others in similar
Hi Chris, yes sure - will do that in the Jira.
I think also the solution is interesting because it shows what's possible
now with more flexible requirejs config on Tapestry side.
One obvious use case for paths is to configure 'local' paths for thirdparty
amd modules which themselves express
Cool! Seems like the right way to go, now that you did almost all the work
anyway :)
On Fri, Nov 22, 2013 at 12:31 PM, Magnus Kvalheim mag...@movellas.comwrote:
Hi Chris, yes sure - will do that in the Jira.
I think also the solution is interesting because it shows what's possible
now with
Hi guys.
Just notised a strange issue with radio ajax/zone submit. It submits all
values - selected and not selected.
- If I disable javascript - then it submits single value. Correct
- If I remove form t:zone then it also submits fine. Correct
If I enable t:zone then it submits all possible
