On Wed, Oct 11, 2006 at 04:35:04PM +0200, Gerald Richter wrote:
> > Line 362 of Embperl/Form/Validate.pm
> >
> > my $default_language = $pref -> {default_language};
> >
> > should be
> >
> > my $default_language = $pref -> {default_language} ||
> > $self->{default_language} ;
> >
>
> Yes, thi
> Line 362 of Embperl/Form/Validate.pm
>
> my $default_language = $pref -> {default_language};
>
> should be
>
> my $default_language = $pref -> {default_language} ||
> $self->{default_language} ;
>
Yes, this make sense. It's updated in the SVN.
>
> But it doesn't say how one should form th
I've been trying out Embperl::Form::Validate, (Embperl version 2.2.0)
and I've found what appears to be a bug with error messages.
If one does not give a $pref argument, and one does not give -msg values
in the RULES array, then all you get for an error message is the id
value of the error message
Gerald,
the JS code for Radio would go something like this:
for ( var i = 0; i < radio_element.length; i ++ ) {
if ( radio_element[i].checked ) return true;
}
the JS code for Select would go something like this:
if ( select_element.selectedIndex != 0 ) return true;
ilia.
On Wed, Oct 16, 20
> there seems to be a bug in the way Embperl::Form::Validate generates the
> client-side javascript code for the radio inputs. The JS code is using
> "value" property, which is not accurate for a Radio object.
>
Yes, radio buttons not supported so far, since they have to be handled
totaly diffe
there seems to be a bug in the way Embperl::Form::Validate generates the
client-side javascript code for the radio inputs. The JS code is using
"value" property, which is not accurate for a Radio object.
ilia.
-
To unsubscribe,
