[
https://issues.apache.org/jira/browse/WICKET-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126171#comment-16126171
]
Kamil commented on WICKET-6449:
-------------------------------
Or putting it in different words:
All the people from https://issues.apache.org/jira/browse/WICKET-1221 who don't
want to handle onError behavior - why would they want to setRequired(true) in
the first place? Especially if it doesn't do anything now.
Why not to leave current behavior as it is (default "not required" checkbox)
and add the required one?
> Form should raise validation error when required checkbox is not set
> --------------------------------------------------------------------
>
> Key: WICKET-6449
> URL: https://issues.apache.org/jira/browse/WICKET-6449
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.0.0-M6
> Reporter: Kamil
> Assignee: Sven Meier
> Attachments: showcase-requiredCheckbox.zip
>
>
> Every user before he registers must agree to terms&conditions, thus proper
> checkbox is required to check and validation error should be raised when
> required checkbox is not checked.
> This test case shows incorrect behavior
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
