Skip Menu |

This queue is for tickets about the Maypole-FormBuilder CPAN distribution.

Report information
The Basics
Id: 14865
Status: new
Priority: 0/
Queue: Maypole-FormBuilder
People
Owner: Nobody in particular
Requestors: rmcclain [...] megapath.net
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.44
Fixed in: (no value)

History Show all quoted text
  Fri Sep 30 18:59:25 2005 Guest - Ticket created
Subject: SET_value changes other field properties
Show quoted text
> 5) As I mentioned before, calling SET_value() on a select list turns it > into a text field. This happens whether you use the + version or not. > Same thing if you use DISABLED or READONLY, except the form value is now > the stringified version of the foreign row. Not sure what happens if > you try to submit.. Didn't test that. >
  Fri Sep 30 19:53:51 2005 cpan.zerofive [...] googlemail.com - Correspondence added
[guest - Fri Sep 30 18:59:25 2005]: Show quoted text
> > 5) As I mentioned before, calling SET_value() on a select list turns
> it
> > into a text field. This happens whether you use the + version or
> not.
> > Same thing if you use DISABLED or READONLY, except the form value is
> now
> > the stringified version of the foreign row. Not sure what happens
> if
> > you try to submit.. Didn't test that. > >
Yes, form_has_a, form_has_many and form_might_have stop processing a field if there are any custom processors, which is a bug. It'll take a little time to sort out, because I know there was some reason for doing that, but I can't remember what it was... It may just have been that I couldn't predict the consequences.