My major concern is how fault tolerant the JSF runtime is. The current JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and produces an invalid partial response. It is really hard to find an error which was hidden by the JSF runtime. The risk of this kind of error increased from almost zero to a frequent one in wildfly 14 (JSF 2.3).
The JSF runtime expected not to make things worse, errors more severe. In this case an incorrect HTML leads to an incorrect partial response, and this is the responsibility of the JSF runtime.
My major concern is how fault tolerant the JSF runtime is. The current JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and produces an invalid partial response. It is really hard to find an error which was hidden by the JSF runtime. The risk of this kind of error increased from almost zero to a frequent one in wildfly 14 (JSF 2.3). The JSF runtime expected not to make things worse, errors more severe. In this case an incorrect HTML leads to an incorrect partial response, and this is the responsibility of the JSF runtime.
Details:
https://github.com/eclipse-ee4j/mojarra/issues/4488
The issue has been closed leaving the problem unsolved, shifting the responsibility onto JSF frameworks like primefaces.