[jira] [Resolved] (WICKET-7159) IFormValidator Skipped When Any Dependent Component is Disabled in Wicket 10.x

["Emond Papegaaij (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij resolved WICKET-7159.
-------------------------------------
    Fix Version/s: 10.6.0
         Assignee: Emond Papegaaij
       Resolution: Fixed

> IFormValidator Skipped When Any Dependent Component is Disabled in Wicket 10.x
> ------------------------------------------------------------------------------
>
>                 Key: WICKET-7159
>                 URL: https://issues.apache.org/jira/browse/WICKET-7159
>             Project: Wicket
>          Issue Type: Bug
>            Reporter: Miroslav Silhavy
>            Assignee: Emond Papegaaij
>            Priority: Major
>             Fix For: 10.6.0
>
>
> Regression causing a breaking behavior in Wicket 10, caused by change WICKET-3899. Discussed here [https://github.com/apache/wicket/pull/1033#discussion_r2104060257].
> Short description
>  * After upgrading to Wicket 10.x, form validators ({{{}IFormValidator{}}}) are not executed if any dependent form component is disabled, due to the addition of an {{isEnabledInHierarchy()}} check. This breaks backward compatibility for applications that rely on validators with conditionally enabled/disabled fields or a field with multiple radio buttons, as the validator is now skipped in these cases. This impacts forms with validation logic and causes migration issues for existing Wicket 9 applications. A flag or configuration to restore the previous behavior, or reverting the change, is needed for backward compatibility.
>  * Common UI patterns with conditionally enabled/disabled fields no longer work with form validators
>  * We must restructure validators and implement complex enabled/disabled field checking in {{getDependentFormComponents()}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)