[
https://issues.apache.org/jira/browse/MYFACES-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649381#comment-17649381
]
Volodymyr Siedlecki commented on MYFACES-4514:
----------------------------------------------
TCK might still fail due to the way it's coded. Test checks where onchange
exists on the element, and it does for the first test.
https://github.com/jakartaee/faces/blob/master/tck/faces22/ajax/src/test/java/ee/jakarta/tck/faces/test/servlet30/ajax/Issue2439IT.java#L42
https://github.com/jakartaee/faces/blob/master/tck/faces22/ajax/src/main/webapp/disabledBehaviors.xhtml#L33-L38
{code:java}
<input id="form1:input1" name="form1:input1" type="text" value="" onchange="">
{code}
> TCK Testing Issue 2: Faces 2.2 - Issue2439IT nested or sequencing f:ajax tags
> different behavior to RI
> ------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-4514
> URL: https://issues.apache.org/jira/browse/MYFACES-4514
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3-next-M7, 4.0.0-RC2
> Environment: Test Setup:
> Apache MyFaces 4.0, Typescript faces.js pull request branch:
> (https://github.com/apache/myfaces/pull/356)
> Tck Tests:
> https://github.com/werpu/tckworkbench
> (compile the 4.0 pr branch and then run the tests via maven in the workbench)
> Reporter: Werner Punz
> Priority: Major
> Fix For: 4.0.0-RC3
>
>
> We have a bug in our impl, a dual f:ajax does not seem to overwrite the
> previous one
> aka the first f:ajax removes an onchange handler in the final result
> the second one should reenable it again, but does not.
> I will file a bug on this one later! (the test explicitely tests for such
> cases)
> <h:inputText id="input2">
> <f:ajax execute="@all" render="@all" disabled="true"/>
> <f:ajax execute="@this" render="@all"/>
> </h:inputText>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
