{"id":12054,"date":"2015-02-01T05:05:30","date_gmt":"2015-01-31T18:05:30","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=12054"},"modified":"2015-05-17T16:22:25","modified_gmt":"2015-05-17T06:22:25","slug":"html-form-multiple-submit-buttons-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/html-form-multiple-submit-buttons-primer-tutorial\/","title":{"rendered":"HTML Form Multiple Submit Buttons Primer Tutorial"},"content":{"rendered":"
\"HTML<\/a>

HTML Form Multiple Submit Buttons Primer Tutorial<\/p><\/div>\n

Today we want to discuss a very old HTML concept called the form<\/i><\/a> tag which allows for the processing of interactive input from the user in the form of textboxes and checkboxes and radio buttons and buttons to transfer information from one webpage to another, somewhere.<\/p>\n

For clarity, today, we only use buttons, and you may ask, “What good are buttons on their own for imparting information?”<\/i> … and will ignore the obvious answer that a button press anywhere, depending on the event logic, can mean so much … after all, we all envisaged the disaster of a nuclear holocaust envisaging the press of one button … no, we want to talk about the idea that you can have more than one input<\/i> tag with type=’submit’<\/i> … and this was not always the case, because in the early days of HTML there was the one submit button<\/i><\/a> allowed on one HTML form … now you can even have more than one form<\/i> … but this is for another day.<\/p>\n

Anyway, you might still ask, anyway, “Ignoring the huge event logic possibilities of a button press (because you are not trying to trick me here), what good are buttons on their own for imparting information?”<\/i> … well, it means on the callback<\/i><\/a> … and today we just callback the same HTML code (via the form<\/i>‘s action=<\/i> designation of itself, today) … as we often like to do at this blog, by the way … we can compartmentalize via the GET<\/i> (in our form’s method<\/i> case … for starters, with POST<\/i> we’d need Ajax<\/a> or a server language, and remember we are trying to keep things more basic here) parameters in the callback<\/i> URL (stored in “Javascript DOM land” as document.URL<\/i><\/a>) according to the value<\/i> of that submit button<\/i> whose name<\/i> becomes that GET<\/i> parameter’s name … so that for an HTML form<\/i>‘s submit button<\/i> like …<\/p>\n


\n<input type='submit' title='Submit of form to an embedded iframe' onclick='cif();' name='submitiframe' id='submitiframe' value='Validate and Iframe'><\/input>
\n<\/code><\/p>\n

… its contributing part of the callback<\/i> URL, in our code, is …<\/p>\n


\n... ?submitiframe=Validate+and+Iframe ...
\n<\/code><\/p>\n

… and so we can, in Javascript, at the onload<\/i> event<\/a>‘s code … have an else if<\/i> statement like …<\/p>\n


\n } else if (document.URL.indexOf('iframe=') != -1) {
\n \/\/ do something here
\n }
\n<\/code><\/p>\n

… to have a good compartmentalizing of “action” segments of code that is quite readable and understandable.<\/p>\n

If the case is not clear … please tee up a live run<\/a> with the HTML programming source code multiple_form_submit_buttons.html<\/a> … or else please try some HTML code yourself … the hardest concept here today is the embedding of an iframe<\/a> in a hierarchical way (note the Javascript DOM manipulation of the form<\/i>‘s target=<\/i> designation, as you examine the downloadable code above), and so for clarity we preface any iframe by a current client (ie. Javascript) timestamp, so you know who inherits who etcetera etcetera etcetera.<\/p>\n

Now even after all this, you may want to say, “So what … an HTML a<\/b><\/a> tag link can do all this.<\/i> … to which we say … that’s true … good to know there is more than one way to “skin a cat” … meowwwwwwww! … “no animals were harmed in the making of this tutorial”<\/font>.<\/p>\n

In fact you could go on and on and on with possibilities for the equivalent means by which to achieve the ends we have here with our HTML, such as using an input<\/i> type=”button”<\/i> or in HTML5, a button<\/i><\/a> tag, and all these and more and more and more and more are worth exploring, and trying, yourself, or by researching the subject. One day, in a real bind, with cross-browser issues, you may need that extra method, to make things work for all the platforms?!<\/p>\n

Did you know?<\/i><\/b><\/p>\n

With an HTML input<\/i> type=”submit”<\/i> (submit button), there is nothing stopping you storing more than just the “front look” of the button in its value<\/i>= parameter. If you want to do this, but there is no way you want to show that “data” as the “front look” of the button, perhaps it really should be an input<\/i> type=”hidden”<\/i><\/a> piece of data, or you should hide it … via style=”display:none;”<\/i><\/a> … Javascript DOM store data to it via document.getElementById([itsID]).value=[myData];<\/i> … and, conditionally perhaps, click it via Javascript, via document.getElementById([itsID]).click()<\/a>;<\/i> method.\n<\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n