Databases
StackOverflow2013
Postsdbo
POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
    primarykey
    data
    text
    <p>Why does the WHATWG disallow nested forms in HTML 4 and HTML5?</p> <p><strong>EDIT</strong>: Problem is originally described at <a href="https://stackoverflow.com/questions/597596/how-do-you-overcome-the-html-form-nesting-limitation">How do you overcome the html form nesting limitation?</a></p> <p><strong>In short author says:</strong> You are making a blog app and you have a form with some fields for creating a new post and a toolbar with "actions" like <strong>"Save"</strong>, <strong>"Delete"</strong>, "Cancel"... The only problem is that pressing "Delete", will submit ALL the form fields on the server even though the only thing needed for this action is a Hidden input with the post-id. </p> <p>So, it is a question about an elegant solution (without JavaScript) for several buttons in a form to submit <strong>different sets of input fields</strong> (like several forms could allow) <strong>and</strong> to line up UI into single entity ("form") from user perspective.</p> <p><strong>Comment from that discussion</strong>: it's almost impossible to completely separate the elements' screen position from their position in the document.</p> <p><strong>EDIT</strong>: I found interesting note <a href="http://anderwald.info/internet/nesting-form-tags-in-xhtml/" rel="nofollow noreferrer">http://anderwald.info/internet/nesting-form-tags-in-xhtml/</a> - that (X)HTML disallows nesting forms like "form > form", but allows "form > fieldset > form", W3 validator says it is valid, but browsers have bugs with such nesting.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USNishi
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
      1. USNishi
      1. VTFavorite
    2. VO
      singulars
      1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
      1. USunexist
      1. VTFavorite
    3. VO
      singulars
      1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou can't blame the WHATWG for HTML4, it didn't even exist when HTML4 was written.
      singulars
      1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
      1. USMs2ger
    2. COIn your blog app example, I would personally just create two <form> elements, basically give your Delete button it's own <form>. I honestly can't see a need for nesting forms when HTML4/5 allows multiple forms anyway.
      singulars
      1. POWhy WHATWG disallows nested forms in HTML 4 and HTML5?
      1. USSunday Ironfoot
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload