Databases
StackOverflow2013
Postsdbo
POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
    primarykey
    data
    text
    <p>I've been a developer for a long time, however forms have always been my least favourite part, more specifically designing them!</p> <p>I'd really like to know how you do you forms, and why. I've had a few discussions with fellow developers over <code>&lt;div&gt;</code> vs <code>&lt;p&gt;</code> on form fields. Which one would you stick with, and why?</p> <p>An example of what I am talking about:</p> <pre><code>&lt;form action="" method="post"&gt; &lt;p&gt; &lt;label for="username"&gt;Username:&lt;/label&gt; &lt;input type="text" name="username" id="username" /&gt; &lt;/p&gt; &lt;p&gt; &lt;label for="submit"&gt;&lt;/label&gt; &lt;input type="submit" name="submit" id="submit" value="Log In" /&gt; &lt;/p&gt; &lt;/form&gt; </code></pre> <p>VS</p> <pre><code>&lt;form action="" method="post"&gt; &lt;div&gt; &lt;label for="username"&gt;Username:&lt;/label&gt; &lt;input type="text" name="username" id="username" /&gt; &lt;/div&gt; &lt;div&gt; &lt;label for="submit"&gt;&lt;/label&gt; &lt;input type="submit" name="submit" id="submit" value="Log In" /&gt; &lt;/div&gt; &lt;/form&gt; </code></pre> <p>When it comes to styling, it seems you can do pretty much the same with both, so is it just personal preference, or is there logic behind using one over the other?</p> <p>Thanks for your time :)</p> <p><strong>UPDATE</strong> I ended up following a nice article on HTML5 forms and have actually found it to allow MUCH better styling of forms. They are much more organised from a development perspective too. For anyone interested, it is located here: <a href="http://24ways.org/2009/have-a-field-day-with-html5-forms">http://24ways.org/2009/have-a-field-day-with-html5-forms</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSk446
    1. USSk446
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. USSk446
      1. VTFavorite
    1. COi think this is a very subjective matter and depends on the developer really. IMHO, i always use fieldsets -> uls and lis to contain each element. so one label and input/select/whatever in each li. while it does provide extra markup, it differentiates my form elements nicely
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. UScorroded
    2. CORelated: [Why use definition lists (DL,DD,DT) tags for HTML forms instead of tables?](http://stackoverflow.com/q/519234)
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. USWesley Murch
    3. COI use lists... always seem to offer a decent way of styling both the form fields and container.
      singulars
      1. POHTML Forms - In your opinion, how should they be done and why? (<div> vs. <p>)
      1. USBen Everard
 

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