[
https://issues.apache.org/jira/browse/TAP5-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312630#comment-14312630
]
Jochen Kemnade commented on TAP5-2450:
--------------------------------------
Just managed to reproduce it by placing the If component inside a Loop that
renders it the first time and doesn't render it the second time:
{code}
<t:loop source="values" value="var:val">
<span t:type="If" test="var:val">
<t:any element="span">foo</t:any>
</span>
</t:loop>
{code}
and
{code}
public List getValues(){
return CollectionFactory.newList(true, false);
}
{code}
{{renderTag}} is not reset to {{false}} after the first iteration. I'll have a
look tomorrow.
> component "If" dont work correct since TAP5-2445 changes
> --------------------------------------------------------
>
> Key: TAP5-2450
> URL: https://issues.apache.org/jira/browse/TAP5-2450
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Sven Homburg
> Attachments: sts-intranet.log
>
>
> since michaels performance changes , the if component dont work as in the
> past like the bottom example.
> {code:title=Page.java}
> @Component(parameters = {"test=condition"}
> private If ifSomethingWrong
> {code}
> {code:title=Page.tml}
> <span t:id="ifSomethingWrong">
> blabla
> </span>
> {code}
> if i use this code, tapestry throws an exception means markup is unbalanced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
