Hi all,
I have one form in which I need two submit buttons with different
behaviour. The first is to submit the form with default
implementation, to do whatever the form needs to do. The second is to
submit the form WITHOUT doing what the form normally does, but
something completely different and
Hi Thorsten,
for a normal form submit the browser should send "bcdHistory.upload" as
post parameter.
That should definitely work. Show us your HTML, maybe something is wrong
there.
Have fun
Sven
On 25.06.20 19:05, Thorsten Schöning wrote:
Hi all,
I have one form in which I need two sub
Guten Tag Sven Meier,
am Donnerstag, 25. Juni 2020 um 23:41 schrieben Sie:
> for a normal form submit the browser should send "bcdHistory.upload" as
> post parameter.
That's what one can read at some places, but my inputs of type
"submit" are not POSTed in different browsers. Neither with nor
wit
Guten Tag Thorsten Schöning,
am Freitag, 26. Juni 2020 um 10:24 schrieben Sie:
> My HTML is pretty much the same, only more bloated because of my use
> case:
I just recognized that Wicket seems to set "name" attributes on inputs
differently on runtime than in my HTML, so I added a non-Wicket
main
Guten Tag Thorsten Schöning,
am Freitag, 26. Juni 2020 um 10:34 schrieben Sie:
>> > name="foobar"
>> value="foobar"
>> title="foobar"
>> />
Using a button instead works as one would expect: When that button is
clicked, the form gets submitted and the name
Hi Thorsten,
this is all HTML standard:
https://stackoverflow.com/questions/2129346
I have no clue why it doesn't work for you.
Please isolate the problem in a jsfiddle or similar.
Have fun
Sven
On 26.06.20 10:44, Thorsten Schöning wrote:
Guten Tag Thorsten Schöning,
am Freitag, 26. Ju
Guten Tag Thorsten Schöning,
am Freitag, 26. Juni 2020 um 10:44 schrieben Sie:
> I don't understand what I'm doing wrong, the plain HTML submit-input
> is pretty much exactly what is documnted elsewhere:
Found the problem: JS-handlers disabled the inputs BEFORE actually
sending the form to not le
