Re: Cougar: ideas for <A>,<INPUT>

Arnoud (galactus@stack.urc.tue.nl)
Tue, 30 Jul 1996 12:50:30 +0200


From: galactus@stack.urc.tue.nl (Arnoud "Galactus" Engelfriet)
To: www-html@w3.org
Subject: Re: Cougar: ideas for <A>,<INPUT>
Date: Tue, 30 Jul 1996 12:50:30 +0200
Message-ID: <2je/x4uYO9wX089yn@stack.urc.tue.nl>

In article <9607291251.ZM2693@gaia.ckm.ucsf.edu>,
"Marc Salomon" <marc@ckm.ucsf.edu> wrote:
> Suggestions for <INPUT>:
> 
> FOR      - IDREF pointing to the form to which this <INPUT> belongs.  Allows
> for
>            placement of <INPUT> elements outside of <FORM>...</FORM> container.

Why would you want to do that? Is this an attempt to work around the
nested form problems? If so, nice idea. I'm not sure how well it would
work, though.

Another proposal, while we're at it:

DEPENDS - IDREF pointing to a form element (INPUT, SELECT, OPTION, FIELDSET
or TEXTAREA) on which this input belongs. If the indicated form element
is not selected, or not filled in, this input should be "greyed out"
until the indicated element is selected.

Example:

<INPUT TYPE=checkbox ID=foo NAME=wantmail> Do you want to receive
an e-mail copy of this form's results?
<P>
<FIELDSET DEPENDS=foo>
Please enter your e-mail address:
<INPUT TYPE=text NAME=email>
</FIELDSET>

Galactus

-- 
To find out more about PGP, send mail with HELP PGP in the SUBJECT line to me.
E-mail: galactus@stack.urc.tue.nl - Please PGP encrypt your mail if you can.
Finger galactus@turtle.stack.urc.tue.nl for public key (key ID 0x416A1A35).
Anonymity and privacy site: <http://www.stack.urc.tue.nl/~galactus/remailers/>