Re: Enhancements to Forms - another loss??

Walter Ian Kaye (walter@natural-innovations.com)
Wed, 12 Feb 1997 12:57:04 -0800 (PST)


Date: Wed, 12 Feb 1997 12:57:04 -0800 (PST)
Message-Id: <199702122057.MAA11850@shellx.best.com>
To: www-html@w3.org
From: walter@natural-innovations.com (Walter Ian Kaye)
Subject: Re: Enhancements to Forms - another loss??

Bruce Leban wrote:
>>From:  galactus@htmlhelp.com (Arnoud Galactus Engelfriet)
>>> While we're on the subject of form enhancements :-), something I've
>>> wanted is an ACTION attribute on the <INPUT TYPE=SUBMIT> tag:
>>>
>>> <INPUT TYPE=SUBMIT ACTION= METHOD=>
>>
>>Why is that necessary? Can't you just assign each submit element
>>a NAME attribute, and distinguish between the various 'actions'
>>in your script depending on which one was pressed?
>
>No. In the examples, I had both http: and https: actions. These have very
>different effects than just using a NAME attribute.

A temporary(?) workaround would be to have a CGI generate the entire
form page, so it could insert the desired action URL.
(I just wrote something like that yesterday in Perl, but of course doing
such a thing requires an understanding of HTML/programming...;)

>>From:  sja20@hermes.cam.ac.uk (James Aylett)
>>This sounds to me a lot like the idea of specifying multiple URL's for a
>>single resource, which I seem to remember being thrown around sometime
>>last year.

>This makes sense. Perhaps the right thing to do is allow alternate values
>for any attribute. This would also be useful for specifying alternate
>versions of pictures:
>   <IMG SRC=x.png> ... x.gif ... lowres-x.gif ...
>Something like
>   <IMG SRC=x.png SRC=x.gif SRC=lowres-x.gif>
>isn't valid, and besides we need a way to attach semantics to the
>alternate attributes so a browser could pick (e.g., highres/lowres). So
>something similar to what I suggested, maybe a <SUBST> tag that
>substitutes attribute values. Something like:
>   (1)  <SUBST other-attributes...>
>   (2)  <SUBST ERROR=problem(s) other-attributes...>

But unfortunately, that's procedural (like JavaScript) not structural
(as HTML is).

I would favor the space-delimited ALTSRC/ALTREF="url#1 url#2 url%20#3"
idea that was one of the suggestions in last year's thread. As to the
related issue of retries, perhaps that could be a stylesheet item?

-Walter
__________________________________________________________________________
    Walter Ian Kaye <boo@best.com>     Programmer - Excel, AppleScript,
          Mountain View, CA                         ProTERM, FoxPro, HTML
 http://www.natural-innovations.com/     Musician - Guitarist, Songwriter