Thanks.  It's good to know that someone else has noticed this oddity.
Sad to say that mny of my user turn off javascript.  So I'm am going to
have to deal with this on the perl side....  I've created a script to
build a hidden field for me that lists all the non-hidden form fields.  So
for the moment I will be using that.  I also plan on creating a module for
my script that will go to the requesting page and read the HTML and
decipher all the appropriate fields.  But this feature will have to be
used sparingly.  Just seems like a lot of work for something that should
have been handled by the browsers.

--Alex

>> The following ideas are options I would _not_ like
>> to follow if possible:
>> - set a default checkbox or redio button (so something is
>> always filled in).
>> - use a hidden field to list of all the fields in the form.
>> - have the perl script read the HTML code from the page and
>> make its own list.
>> - javascript
>>
>> I kinda understand why the browser doesn't send this
>> information (no value
>> to hold onto), but there HAS to be a solution for this.
>> Seems frightfully
>> stupid not to have an easy option out there for something like this.
>
> No solution other than the ones you mentioned, that I'm aware of.
> What we've done is generally a hidden field that gets fiddled with via
> JavaScript when the checkbox is changed.  Then the back-end code just
> looks
> at the hidden field, and can be totally oblivious to what's really going
> on
> in the HTML.
> Yup, seems stupid to me, each time I run into it again, too.
> I'd be curious if someone has come up with something better.
> Doubtful, though.
> good luck                             philipp
>

 
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm

Reply via email to