t:formdata is writeen twice if a formfragment is used in a form wich zone
parameter is defined
----------------------------------------------------------------------------------------------
Key: TAP5-350
URL: https://issues.apache.org/jira/browse/TAP5-350
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.15
Reporter: Stéphane Decleire
This small piece of code shows the second t:formdata hidden field :
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
<body>
<t:form zone="myzone">
<t:label for="field1"/> : <t:textfield t:id="field1"/>
<t:checkbox t:id="moreFieldsSwitch" t:mixins="triggerfragment"
fragment="moreFields"/>
<t:label for="moreFieldsSwitch">more fields ?</t:label>
<t:formfragment t:id="moreFields" visible="moreFieldsSwitch">
<t:label for="field2"/> : <t:textfield t:id="field2"/>
</t:formfragment>
<input type="submit"/>
</t:form>
</body>
</html>
public class TestFragment {
@Persist @Property private String field1;
@Persist @Property private String field2;
@Persist @Property private boolean moreFieldsSwitch;
}
This results in the following XHR response seen in Firebug :
field1 test
field2
moreFieldsSwitch on
t:formdata
H4sIAAAAAAAAAFvzloG1XJRBOCS1uMStKDE9NzWvxCotMzUnxbC4iME0vyhdL7EgMTkjVa8ksQCopqjSVC85vyg1JzNJLymxOFXPMQkomJhc4gbSoxKcWlJaoBp6mPuh6PE/TAyMPgzcyfl5JUX5OX6JuaklDEI+WYllifo5iXnp+sElRZl56dYVBSUMbBAbcTvEkVSHBBTlJ6cWFweXJuVmFhdn5ucdXpdikvZt3jkmBoaKgnJ5BlkUi3KBJoEtKy4uzyxJziguZKhjYChhEABJgE0sDgZLENQJ0sgKACYX5qFWAQAA
t:formdata
H4sIAAAAAAAAAFvzloG1XJRBOCS1uMStKDE9NzWvxCotMzUnxai4iME0vyhdL7EgMTkjVa8ksQCopqjSVC85vyg1JzNJLymxOFXPMQkomJhc4gbSoxKcWlJaoBp6mPuh6PE/TAyMPgzcyfl5JUX5OX6JuaklDEI+WYllifo5iXnp+sElRZl56dYVBSUMbBAbcTvEkVSHBBTlJ6cWFweXJuVmFhdn5ucdXpdikvZt3jkmBoaKgnJ5BlkUi3KBJoEtKy4uzyxJziguZKhjYChhEABJgE0sDgZLENQJ0sgKACYX5qFWAQAA
and the second t:formdata is a copy of the first one or is empty. It seems to
depend of the initial state of the fragment.
Stephane
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
