[
https://issues.apache.org/jira/browse/MYFACES-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677412#comment-17677412
]
Werner Punz edited comment on MYFACES-4519 at 1/16/23 2:25 PM:
---------------------------------------------------------------
It was my fault, I was on the wrong branch when I filed this test (4.0.0
instead of master).
Master already has it fixed, which my selenium fixes now target. Other "stable"
branches still have the problem. Whether they are going to fix this for 4.0.0
or 4.0.1 for instance I cannot say.
Master definitely does not have the problem anymore (see also my comment in:
[https://github.com/jakartaee/faces/issues/1777)]
was (Author: werpu):
It was my fault, I was on the wrong branch when I filed this test (4.0.0
instead of master).
Master already has it fixed, which my selenium fixes now target. Other "stable"
branches still have the problem. Whether they are going to fix this for 4.0.0
or 4.0.1 for instance I cannot say.
Master definitely does not have th eproblem anymore (see also my comment in:
[https://github.com/jakartaee/faces/issues/1777)]
> TCK Testing Issue 8: Faces 4.0 - Spec1567IT: Nested f:ajax does not resolve
> the render properly
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-4519
> URL: https://issues.apache.org/jira/browse/MYFACES-4519
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
>
> More Details see:
> [https://github.com/apache/myfaces/pull/356#issuecomment-1338988239]
> bottom
> The problem seems to be that the f:ajax is within a composite component and
> being passed down...
> The render gets lost along the way.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
