That case should not be done with required in my eyes, thats a data
check that should have a specific value (true in this case). So thats
an other data validator (just like range validator for a number)
On 1/8/08, Sam Barnum <[EMAIL PROTECTED]> wrote:
> Right, like for an "accept terms" checkbox a
Right, like for an "accept terms" checkbox after some legalese stuff,
for example.
On Jan 7, 2008, at 5:09 PM, Kent Tong wrote:
Dan Kaplan-3 wrote:
But another way to look at it is this: When a checkbox is
unchecked, it
has
a value of "unchecked". Therefore, if you setRequired=true o
Dan Kaplan-3 wrote:
>
> But another way to look at it is this: When a checkbox is unchecked, it
> has
> a value of "unchecked". Therefore, if you setRequired=true on a checkbox,
> it's always satisfied. In otherwords, a checkbox always has a value so
> setRequired=true has no effect on a chec
The problem is that this setRequired is only really valid for a try
state checkbox. I agree that required shouldnt mean it has to be true
thats weird in my eyes
On 1/7/08, Kent Tong <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I observed that if "required" is set to true for a Checkbox, Wicket will
> en
riginal Message-
From: Kent Tong [mailto:[EMAIL PROTECTED]
Sent: Monday, January 07, 2008 2:07 AM
To: users@wicket.apache.org
Subject: "required" for Checkbox
Hi,
I observed that if "required" is set to true for a Checkbox, Wicket will
ensure that the Checkbox is checked. If
Hi,
I observed that if "required" is set to true for a Checkbox, Wicket will
ensure that the Checkbox is checked. If it is cleared by the user, it
will be treated as an error. See
https://issues.apache.org/jira/browse/WICKET-1221 and
https://issues.apache.org/jira/browse/WICKET-1260 for some
bac
