From: Thomas 'PointedEars' Lahn on
Doug Miller wrote:

> The Natural Philosopher wrote:
>> I think I dint make myself clear. With js I can fire an evfent handler.,
>> set any amount of post variables, and do a submit. I can even submit to
>> a totally different target or spawn a popup window.
>>
>> With strict HTML one button=one vale,
>
> No. The array of POST variables sent to the server includes all named
> input elements in the form, regardless of how many submit buttons there
> are.

There is no "array of POST variables". The message body of an HTTP POST
request is a string, with a HTML form it is usually

name1=value1&name2=value2

etc., with names and values URL-encoded. It is only the server-side
application, e.g. PHP, that makes an (associative) array (e.g.,
$HTTP_POST_VARS or $_POST) out of it.


PointedEars
--
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
-- from <http://www.vortex-webdesign.com/help/hidesource.htm> (404-comp.)
From: Doug Miller on
In article <4753046.FLt9SDvczp(a)PointedEars.de>, Thomas 'PointedEars' Lahn <cljs(a)PointedEars.de> wrote:
>Doug Miller wrote:
>
>> The Natural Philosopher wrote:
>>> I think I dint make myself clear. With js I can fire an evfent handler.,
>>> set any amount of post variables, and do a submit. I can even submit to
>>> a totally different target or spawn a popup window.
>>>
>>> With strict HTML one button=one vale,
>>
>> No. The array of POST variables sent to the server includes all named
>> input elements in the form, regardless of how many submit buttons there
>> are.
>
>There is no "array of POST variables".

From the perspective of a server-side script, there certainly is (e.g. $_POST
in PHP).

>The message body of an HTTP POST
>request is a string, with a HTML form it is usually
>
> name1=value1&name2=value2
>
>etc., with names and values URL-encoded. It is only the server-side
>application, e.g. PHP, that makes an (associative) array (e.g.,
>$HTTP_POST_VARS or $_POST) out of it.

I'm afraid you've missed the point altogether, which is that I was correcting
the previous poster's misapprehension that only one value could be transmitted
per submit button.
From: Thomas 'PointedEars' Lahn on
Doug Miller wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Doug Miller wrote:
>>> The Natural Philosopher wrote:
>>>> I think I dint make myself clear. With js I can fire an evfent
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> handler., set any amount of post variables, and do a submit. I can even
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> submit to a totally different target or spawn a popup window.
>>>>
>>>> With strict HTML one button=one vale,
>>> No. The array of POST variables sent to the server includes all named
>>> input elements in the form, regardless of how many submit buttons there
>>> are.
>> There is no "array of POST variables".
>
> From the perspective of a server-side script, there certainly is (e.g.
> $_POST in PHP).

The perspective was not any server-side application here.

>> The message body of an HTTP POST
>> request is a string, with a HTML form it is usually
>>
>> name1=value1&name2=value2
>>
>> etc., with names and values URL-encoded. It is only the server-side
>> application, e.g. PHP, that makes an (associative) array (e.g.,
>> $HTTP_POST_VARS or $_POST) out of it.
>
> I'm afraid you've missed the point altogether, which is that I was
> correcting the previous poster's misapprehension that only one value could
> be transmitted per submit button.

No, I did notice that. Your answer was partially wrong anyway (as the
question was completely wrong).


PointedEars
--
Anyone who slaps a 'this page is best viewed with Browser X' label on
a Web page appears to be yearning for the bad old days, before the Web,
when you had very little chance of reading a document written on another
computer, another word processor, or another network. -- Tim Berners-Lee
From: The Natural Philosopher on
Doug Miller wrote:
> In article <hgrehi$rlh$1(a)news.albasani.net>, The Natural Philosopher <tnp(a)invalid.invalid> wrote:
>> Swifty wrote:
>>> JR wrote:
>>>> But `post` can only be used within a form, I think.
>>> Indeed, but if you *want* the "Submit" button to look like a link, you
>>> can do that simply enough with CSS (I could do it, which is my
>>> definition of "simply enough").
>>>
>> Problem I have with the submit button, is that if you style it with an
>> image of non square shape, with a transparent edge to it, what shows
>> through is NOT the background image of the containing element, but the
>> plain background COLOR of the containing element. Or possibly the
>> background color of the button itself. Hmm. Perhaps that's the problem.
>
> Perhaps the problem is how you've defined the button.Do you have
> <input type="submit"...> or <input type="image"...> ?

Input type submit Doug.

I've just glanced through the code, and there is no background colour at
a deeper level of nesting than the main background image: So its a
'feature' of all browsers that a styled button with transparency on its
image, doesn't honor the background image behind it.
I.e. If you have e,g.

<div class="with_background_image">
<input class="with_different_background_image_with_transparent_bits"
type="submit">
</div>

What shows through the transparent bits is the last set background
colour. Not the last set background image.


From: The Natural Philosopher on
Thomas 'PointedEars' Lahn wrote:
> Doug Miller wrote:
>
>> The Natural Philosopher wrote:
>>> I think I dint make myself clear. With js I can fire an evfent handler.,
>>> set any amount of post variables, and do a submit. I can even submit to
>>> a totally different target or spawn a popup window.
>>>
>>> With strict HTML one button=one vale,
>> No. The array of POST variables sent to the server includes all named
>> input elements in the form, regardless of how many submit buttons there
>> are.
>
> There is no "array of POST variables".

Muy Bad, that's how they appear in PHP, of course, but you are perfectly
right.

The message body of an HTTP POST
> request is a string, with a HTML form it is usually
>
> name1=value1&name2=value2
>
> etc., with names and values URL-encoded. It is only the server-side
> application, e.g. PHP, that makes an (associative) array (e.g.,
> $HTTP_POST_VARS or $_POST) out of it.
>

Correct, as always, Thomas. ;-)

>
> PointedEars