Databases
StackOverflow2013
Postsdbo
POBest way to structure a two column html form?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest way to structure a two column html form?
    primarykey
    data
    text
    <p>What is the best way to align the following?</p> <p>I want the <code>.inputTitle</code> on the left and the <code>inputInput</code> on the right with the error inbetween them both.</p> <p><strong>CSS:</strong></p> <pre><code>.crud_form{ width:430px; margin:10px solid; font-family:Verdana, Geneva, sans-serif; background:orange; } .inputTitle{ float:left; clear:left; margin:11px 10px 10px 0; width:95px; background:green; } .inputRequired{ float:left; margin:5px; width:113px; background:blue; } .inputError{ float:left; margin:10px; background:red; } .crud_form select textarea{ float:left; clear:both; } </code></pre> <p><strong>HTML:</strong></p> <pre><code>&lt;form action="#" method="post" accept-charset="utf-8" class="crud_form" enctype="multipart/form-data"&gt; &lt;span class="inputTitle"&gt;First Name&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;input type="text" name="first_name" value="" id="first_name" /&gt;&lt;/span&gt;&lt;span class="inputError"&gt;&lt;/span&gt; &lt;span class="inputTitle"&gt;Last Name&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;input type="text" name="last_name" value="" id="last_name" /&gt;&lt;/span&gt;&lt;span class="inputError"&gt;&lt;/span&gt; &lt;span class="inputTitle"&gt;Address&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;textarea name="address" cols="40" rows="10" id="address" &gt;&lt;/textarea&gt;&lt;/span&gt;&lt;span class="inputError"&gt;&lt;/span&gt; &lt;span class="inputTitle"&gt;Phone&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;input type="text" name="phone" value="" id="phone" /&gt;&lt;/span&gt;&lt;span class="inputError"&gt;&lt;/span&gt; &lt;span class="inputTitle"&gt;Item&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;select name="item" id="item"&gt; &lt;option value="Caps cost $15"&gt;&lt;/option&gt; &lt;option value="Mugs cost $20"&gt;&lt;/option&gt; &lt;option value="Childrens T-shirts, sizes 0 to 6"&gt;$10&lt;/option&gt; &lt;option value="Ladies (no photo) cost $20"&gt;&lt;/option&gt; &lt;option value="Men cost $20"&gt;&lt;/option&gt; &lt;/select&gt;&lt;/span&gt; &lt;span class="inputError"&gt;&lt;/span&gt; &lt;span class="inputTitle"&gt;Comments&lt;/span&gt;&lt;span class="inputInput"&gt;&lt;textarea name="comments" cols="40" rows="10" id="comments" &gt;&lt;/textarea&gt;&lt;/span&gt;&lt;span class="inputError"&gt;&lt;/span&gt; &lt;input type="submit" value="Save" /&gt; &lt;/form&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMoses
    1. USJess McKenzie
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COConsider a self-contained [fiddle](http://jsfiddle.net) too.
      singulars
      1. POBest way to structure a two column html form?
      1. USKirk Woll
    2. COAside: please use proper labels explicitly associated with the related input instead of a generic span: `<label class="inputTitle" for="last_name">Last Name</label>`. This is not only is nice for your users, but since the labels are programmatically associated with the inputs, and not dependent upon proximity, it gives you more latitude to arrange the markup.
      singulars
      1. POBest way to structure a two column html form?
      1. USsteveax
    3. CO@steveax I totally agree with using labels as they improve UX. However, you make it sound like it's a good thing to have labels a long distance away from their content, which doesn't make any sense to me.
      singulars
      1. POBest way to structure a two column html form?
      1. USMoses
 

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