Skip to main content

Why is the form not preventing submission?



I have a basic form that I am using as a dummy to test some JavaScript functionality. My goal is to click the submit button and have submission paused until a javascript function is executed, then submit the form after that. the code I currently have is below, but the submission of the form is not prevented, and the hidden field's value is never set. can someone explain why this is happening?





NOTE I am aware of a jQuery method of performing the same functionality. I am specifically trying to solve this problem without using jQuery. If your only answer is "jQuery is better", please do not bother.







<html>

<head>

<script type="text/javascript">

function test(){

document.getElementById("hidden").value="hidden";



var queryString = $('#decisionform').formSerialize();

alert(queryString);



document.getElementById("form").submit();

}

</script>

</head>



<body>



<?php

if ($_POST){

foreach ($_POST as $key=>$value){

echo "<b>$key</b> $value<br>";

}

}

?>



<form action="hello.php" method="post" id="form">

<input name="first" type="text" />

<input name="second" type="text" />

<input name="third" type="text" />

<input name="hidden" type="hidden" />

<input name="submit" type="submit" value="Submit" onclick="test();return false;" />

</form>



</body>

</html>




Comments

  1. You don't have an element with the id hidden so document.getElementById("hidden").value="hidden"; will throw an error as you can't set properties on undefined. The script will stop running and never reach return false so the form will submit as normal.

    ReplyDelete
  2. try <form action="hello.php" method="post" id="form" onsubmit="test(); return false;">

    to prevent a submit, you actually need to have a return false, in the onsubmit even of the form itself

    along with not having an id on the hidden field.

    ReplyDelete
  3. <input name="submit" type="submit" value="Submit" onclick="test();return false;" />


    use a regular button in this case because your function is performing the submit.

    <input name="submit" type="button" value="Submit" onclick="test()" />

    ReplyDelete
  4. You're missing the id attribute from your input element. Modify <input name="hidden" type="hidden" /> to <input name="hidden" type="hidden" id="hidden" />.

    ReplyDelete
  5. You can use

    onclick="return test()"


    and just return false at the end of the function.

    ReplyDelete
  6. Add id="hidden" to your input, like this:

    <input name="hidden" type="hidden" id="hidden" />

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex