<button type=submit...> and <input type=submit ...>

[Mattia]

Hi!
I have a <form> that can be submitted thruogh three buttons and I need
to tell witch one was pressed when the form was submitted. I now do it
with 3 <input type="submit" name="..." value="...">

with <input type="submit" ...> the only name-value values submitted
(pushed into the query string) is the one of the submit button that was
pushed (if you have many of them).

Ex:
<form ...>
<input type="text" .../>
<input type="submit" name="a" value="click".. ./>
<input type="submit" name="b" value="click2". ../>
<input type="submit" name="c" value="click3". ../>
</form>

in a form like this I can easily distinguish what button was used to
submit the form AFTER SUBMITTING.
but with <button type="submit" name="..." .... > click! </button> all
the name-innertext values are submitted (pushed to the query string)

Ex:
<form ...>
<input type="text" .../>
<button type="submit" name="a"> click </button>
<button type="submit" name="b"> click2 </button>
<button type="submit" name="c"> click3 </button>
</form>

What ways do I have to distinguish what button was used to submit the
form AFTER SUBMITTING?

Is there a way to do it without using javascript?
--
Mattia <ma******@liber o.it>
http://www.chiacchierando.com/

[Jukka K. Korpela]

Mattia <ma******@liber o.it> wrote:

I have a <form> that can be submitted thruogh three buttons and I need
to tell witch one was pressed when the form was submitted. I now do it
with 3 <input type="submit" name="..." value="...">
Fine.
<input type="submit" name="a" value="click".. ./>
<input type="submit" name="b" value="click2". ../>
<input type="submit" name="c" value="click3". ../>
</form>

in a form like this I can easily distinguish what button was used to
submit the form AFTER SUBMITTING.
Yes indeed. You have made it double sure by using different name attributes
_and_ different value attributes. (Either of them would suffice.) The user
may have difficulties in understanding BEFORE SUBMITTING what click, click2,
and click3 mean. :-)
but with <button type="submit" name="..." .... > click! </button> all
the name-innertext values are submitted (pushed to the query string)
Browsers are known to misbehave in this area. The specifications aren't
absolutely crystal clear either - are such elements really "submit buttons"?
What ways do I have to distinguish what button was used to submit the
form AFTER SUBMITTING?

Is there a way to do it without using javascript?

Why do you postulate that javascript could help here?

Anyway, you describe that you now have a working solution. Just stick to it,
and don't create problems by switching to <button>. Simple as that.

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

[Salagir]

On Mon, 10 Nov 2003 00:48:35 +0000 (UTC), in
comp.infosystem s.www.authoring.html, Jukka K. Korpela wrote:

in a form like this I can easily distinguish what button was used to
submit the form AFTER SUBMITTING.
but with <button type="submit" name="..." .... > click! </button> all
the name-innertext values are submitted (pushed to the query string) Browsers are known to misbehave in this area. The specifications aren't
absolutely crystal clear either - are such elements really "submit buttons"?

I think they are and it's quite clear: just send a variable if clicked

What ways do I have to distinguish what button was used to submit the
form AFTER SUBMITTING?
Is there a way to do it without using javascript?

Why do you postulate that javascript could help here?

Because it does.
My same problem, on this same newsgroup:

http://tinylink.com/?CwT8jobe3S or
msg-id <sl************ *******@choam.e frei.fr>

My php solution (msg in french, but php is still php):
I use javascript for IE and buttons for the others

http://groups.google.com/groups?selm...choam.efrei.fr
or msg-id <sl************ ********@choam. efrei.fr>
Anyway, you describe that you now have a working solution. Just stick to it,
and don't create problems by switching to <button>. Simple as that.

If you can, yes, that's even better :)

--
++++++++ Zelda, Dragon Ball, Mana and my (art)work at www.salagir.com ++++++++

[Jukka K. Korpela]

Salagir <Sa*****@jeruCI TEDELESPACE.org .invalid> wrote:

Browsers are known to misbehave in this area. The specifications
aren't absolutely crystal clear either - are such elements really
"submit buttons"?

I think they are and it's quite clear: just send a variable if clicked

No, that's certainly not true. There is no requirement that clicking would
be the only possibility of activating an element. You seem to have a rather
simplistic view on the situation - that's why it looks clear to you.

Why do you postulate that javascript could help here?

Because it does.

It cannot, of course. You are apparently not considering the issue within
the context of this group, which is HTML authoring for the _World Wide Web_.
Postulating that a particular client-side scripting language is supported by
the browser and enabled means that you are not thinking in WWW terms.

Anyway, you describe that you now have a working solution. Just stick
to it, and don't create problems by switching to <button>. Simple as
that.

If you can, yes, that's even better :)

Why would it be a matter of being able to do something? Exactly what would
be needed for continuing the use of a simple, robust solution, as opposite
to changing it to a <button> problem?

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

[Salagir]

On Mon, 10 Nov 2003 11:19:10 +0000 (UTC), in
comp.infosystem s.www.authoring.html, Jukka K. Korpela wrote:

Salagir <Sa*****@jeruCI TEDELESPACE.org .invalid> wrote:

The specifications aren't absolutely crystal clear either I think they are and it's quite clear: just send a variable if clicked

No, that's certainly not true. There is no requirement that clicking would
be the only possibility of activating an element.

Of course, by saying "if clicked" I meant "if the form was submitted
using the specific button created by this tag" ;)
You seem to have a rather
simplistic view on the situation - that's why it looks clear to you.

Yes, but isn't html simple ? ;) That's why it works.

Why do you postulate that javascript could help here?

Because it does.

It cannot, of course. You are apparently not considering the issue within
the context of this group, which is HTML authoring for the _World Wide Web_.
Postulating that a particular client-side scripting language is supported by
the browser and enabled means that you are not thinking in WWW terms.

In what follows, I use javascript only with IE, considering that the
others browsers... respect w3c. And I don't consider IE users as people
bright enought to disable javascript. I they are, they're bright enought
to use a real browser.

If you can, yes, that's even better :)

Why would it be a matter of being able to do something? Exactly what would
be needed for continuing the use of a simple, robust solution, as opposite
to changing it to a <button> problem?

Well, I don't know exactly what he intends to do.

Plus, button can make nice things like puttings images and html text in
it.. and I think it's cool, sorry ;)

--
++++++++ Zelda, Dragon Ball, Mana and my (art)work at www.salagir.com ++++++++
Hi! Je voudrais une crêpe au chocolat fruits de mer, s'il vous plait!

[Alan J. Flavell]

On Mon, 10 Nov 2003, Salagir wrote:

On Mon, 10 Nov 2003 00:48:35 +0000 (UTC), in
comp.infosystem s.www.authoring.html, Jukka K. Korpela wrote:

Why do you postulate that javascript could help here?
Because it does.

You can't have been reading this group for long! In a WWW context,
it's a mistake to make Javascript a mandatory part of any solution.

Optional extras are a different matter, but that doesn't seem to be
what we have here.

My reaction to your posting was that you already had a competent
solution, and now seemed to be looking for a way to break it.
I use javascript for IE and buttons for the others

Not on my IE, you won't. When Billware alerts me with the ominous
alert message "Scripts are usually safe", I read that as "scripts are
sometimes disastrous - would I want to run scripts from a site that
has, as yet, given me no reason to trust it?".

[Salagir]

On Mon, 10 Nov 2003 11:00:42 +0000, in comp.infosystem s.www.authoring.html,
Alan J. Flavell wrote:

I use javascript for IE and buttons for the others

Not on my IE, you won't. When Billware alerts me with the ominous
alert message "Scripts are usually safe", I read that as "scripts are
sometimes disastrous - would I want to run scripts from a site that
has, as yet, given me no reason to trust it?".

Why do you use this "biggest spyware and security hole usable" for a
browser then ?
I enable javascript with firebird and was never bothered by any pop-up
and others. For some little details, javascript can be usefull, and if
there is a real problem, I disable javascript with one click.

(omg did I just begin a troll??)
--
++++++++ Zelda, Dragon Ball, Mana and my (art)work at www.salagir.com ++++++++
<\slick> 3d studio max install told me to close all program when
installing, so i just opened more to be defiant
<\slick> take that

[Alan J. Flavell]

On Mon, 10 Nov 2003, Salagir wrote:

On Mon, 10 Nov 2003 11:00:42 +0000, in comp.infosystem s.www.authoring.html,
Alan J. Flavell wrote:

I use javascript for IE and buttons for the others Not on my IE, you won't. When Billware alerts me with the ominous
alert message "Scripts are usually safe", I read that as "scripts are
sometimes disastrous - would I want to run scripts from a site that
has, as yet, given me no reason to trust it?".

Why do you use this "biggest spyware and security hole usable" for a
browser then ?

OK: normally, I use Mozilla. Sometimes I need to use IE. I chose to
present the IE scenario since it's closer to what (statistically)
most users would be starting from. After all, this isn't supposed to
be about me, alone, personally, but about j.random.cautio us.webnaut.
We don't, of course, know what security settings they choose, but
after a few trojan infections and OS re-installations they might start
to get some kind of message.

Both of those browsers have options to disable scripting. Indeed,
every browser has an option to disable scripting: just stick it behind
an appropriate proxy.
I enable javascript with firebird and was never bothered by any pop-up
Oh, I enabled those warnings quite deliberately by choice. I _want_
to be bothered when someone's trying to execute untrusted code on my
computer.
and others. For some little details, javascript can be usefull,

You seem to have overlooked the fact that this is an _authoring_
discussion group, and what's more, in a *WWW* context. You don't get
anywhere by arguing with users as to whether they are going to allow
you to execute your javascript on their computer. You do better to
adapt your authoring so that they get the substantive part of your
content.

[Mattia]

thanks Salagir!

Well, I don't know exactly what he intends to do.

I will do what Salagir sugested to do!
The problem was: I had a working form with <input type="submit" ..> and
wanted to improve the look of it by substituting it with a <button> tag,
because in a <button> tag you can insert formatted text, images...

Salagir gave me a solution, Jukka gave me nothing.

Jukka, i know that rich text, images and javascript hurt your soul of
"pure HTML" programmer. I know you want everything to be plain text, but
that's now what I want, that's not what my customers want, that's not
what my boss wants. Maybe they're all stupid,
but this is the way the world goes.

Thank you for all the information.

--
Mattia <ma******@liber o.it>
http://www.chiacchierando.com/

[Jukka K. Korpela]

Mattia <ma******@liber o.it> wrote:

Salagir gave me a solution, Jukka gave me nothing.
I cannot give you the right answer, if you are not willing to receive it.
(We note, en passant, that you don't post the URL of your purported solution
[i.e., a non-solution to a non-problem].)
Jukka, i know that rich text, images and javascript hurt your soul of
"pure HTML" programmer.

We are not on a first name basis, but thanks anyway for telling that you
don't even know what HTML is. Please do not stop using your current
malformed From field until you have something to say about HTML authoring
for the World Wide Web.

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html