Can we use any other TAG in `&lt;ul&gt;` along with `&lt;li&gt;`?

like

    &lt;ul&gt;
    Some text here or &lt;p&gt;Some text here&lt;p&gt; etc
    &lt;li&gt;item 1&lt;/li&gt;
    Some text here or &lt;p&gt;Some text here&lt;p&gt; etc
    &lt;li&gt;item 1&lt;/li&gt;
    &lt;/ul&gt;



Can we use any other TAG inside &lt;ul&gt; along with &lt;li&gt;?

How can space and tab be represented in an XML tag?

Are there any special characters that can represent them?

Represent space and tab in XML tag?

I have a unicode string like &quot;Tanım&quot; which is encoded as &quot;Tan%u0131m&quot; somehow. How can i convert this encoded string back to original unicode. 
Apparently urllib.unquote does not support unicode.

How to unquote a urlencoded unicode string in python?

`input type=&quot;submit&quot;` and `button` tag are they interchangeable? or if there is any difference then When to use `input type=&quot;submit&quot;` and when `button` ?

And if there is no difference then why we have 2 tags for same purpose?

input type=&quot;submit&quot; Vs button tag are they interchangeable?

Regarding `window.innerWidth` and `document.documentElement.clientWidth`,


1. Webkit (Chrome / Safari) claims `innerWidth` is smaller than `clientWidth`. 

1. Trident and Presto claim `innerWidth` is bigger than `clientWidth`. 

1. Gecko claims `innerWidth` is the same size as `clientWidth`.

What is the *correct* behavior **stated by** W3C (or silimar &quot;authority&quot;)?

Test Script ([on JSFiddle][1]) (on [GoogleHost][2]):

&lt;!-- begin snippet: js hide: false --&gt;

&lt;!-- language: lang-js --&gt;

    setInterval(function() {
      var inner_w = window.innerWidth;
      var inner_h = window.innerHeight;
      var client_w = document.documentElement.clientWidth;
      var client_h = document.documentElement.clientHeight;
      var debug_msg = &quot;inner: &quot; + inner_w + &quot;-&quot; + inner_h + &quot;&lt;br&gt;client: &quot; + client_w + &quot;-&quot; + client_h;
      document.getElementById(&quot;d&quot;).innerHTML = debug_msg;
      document.title = debug_msg;
      document.body.style.background = (client_w === inner_w &amp;&amp; client_h === inner_h ? &quot;green&quot; : &quot;red&quot;);
    }, 60);

&lt;!-- language: lang-html --&gt;

    &lt;div id=&quot;d&quot;&gt;&lt;/div&gt;

&lt;!-- end snippet --&gt;

(Run the snippet in **full page mode** and un-maximize or &quot;restore&quot; the window. Observe `debug_msg` while dragging the edge of the window to resize it.)


  [1]: https://jsfiddle.net/cgp9h0oe/
  [2]: http://googledrive.com/host/0B53jM4a9X2fqZENLRFBlOEZhVU0

window.innerWidth vs document.documentElement.clientWidth

In HTML5 we currently have a `&lt;figure&gt;` element, defined like so ([W3C reference][1]) 

&gt; The figure element represents a unit of content, optionally with a caption, that is self-contained, that is typically referenced as a single unit from the main flow of the document, and that can be moved away from the main flow of the document without affecting the document’s meaning.


Recently a new element `&lt;picture&gt;` was proposed by the [Responsive Images Community group][2] and it was defined [in the reference][3] like so

&gt; The picture element used for displaying an image that can come from a range of sources (see srcset attribute). Which image the user agent displays depends on the algorithm for deriving the source image. 

Since the two descriptions seems to be not contradictory (and documentation on picture is on *draft* state yet) here my question: is it possible (technically and semantically) to have a nested `picture` inside a `figure` element, in this way?

    &lt;figure&gt;
       &lt;picture&gt;
          &lt;source ...&gt;
          &lt;source ...&gt;
          &lt;source ...&gt;
          &lt;img..&gt;
       &lt;/picture&gt;
    
       &lt;figcaption&gt;...&lt;/figcaption&gt;
    &lt;/figure&gt;

I&#39;ve found no references about it in specs. :\

Note: I&#39;m aware that no browser implements currently this element, I&#39;m just making some experiments with [jQuery picture][4]  

Thank you.


  [1]: http://dev.w3.org/html5/markup/figure.html
  [2]: http://www.w3.org/community/respimg/
  [3]: http://dvcs.w3.org/hg/html-proposals/raw-file/tip/responsive-images/responsive-images.html#the-picture-element
  [4]: http://jquerypicture.com/

Use of &lt;picture&gt; inside &lt;figure&gt; element in HTML5?

Which of the following should I use in my stylesheets?

    /* Example #1: */ background-image: url(image.png);
    /* Example #2: */ background-image: url(&quot;image.png&quot;);
    /* Example #3: */ background-image: url(&#39;image.png&#39;);

What does the W3C specify as the *correct way*?

Is quoting the value of url() really necessary?

Consider the main axis and cross axis of a flex container:

[![An illustration of the various directions and sizing terms as applied to a row flex container][2]][2]
&lt;sub&gt;Source: [W3C][3]&lt;/sub&gt;

To align flex items along the main axis there is one property:

 - [`justify-content`](https://www.w3.org/TR/css-flexbox-1/#justify-content-property)

To align flex items along the cross axis there are three properties:

 - [`align-content`](https://www.w3.org/TR/css-flexbox-1/#align-content-property)
 - [`align-items`](https://www.w3.org/TR/css-flexbox-1/#align-items-property)
 - [`align-self`](https://www.w3.org/TR/css-flexbox-1/#align-items-property)

In the image above, the main axis is horizontal and the cross axis is vertical. These are the default directions of a flex container.

However, these directions can be easily interchanged with the [`flex-direction`](https://www.w3.org/TR/css-flexbox-1/#propdef-flex-direction) property.

    /* main axis is horizontal, cross axis is vertical */
    flex-direction: row;
    flex-direction: row-reverse;

    /* main axis is vertical, cross axis is horizontal */    
    flex-direction: column;
    flex-direction: column-reverse;

(The cross axis is always perpendicular to the main axis.)

My point in describing how the axes&#39; work is that there doesn&#39;t seem to be anything special about either direction. Main axis, cross axis, they&#39;re both equal in terms of importance and `flex-direction` makes it easy to switch back and forth. 

*So why does the cross axis get two additional alignment properties?*

*Why are `align-content` and `align-items` consolidated into one property for the main axis?*

*Why does the main axis not get a `justify-self` property?*

---

Scenarios where these properties would be useful:

 - placing a flex item in the corner of the flex container&lt;br&gt;
`#box3 { align-self: flex-end; justify-self: flex-end; }`

 - making a group of flex items align-right (`justify-content: flex-end`) but have the first item align left (`justify-self: flex-start`)

 *Consider a header section with a group of nav items and a logo. With `justify-self` the logo could be aligned left while the nav items stay far right, and the whole thing adjusts smoothly (&quot;flexes&quot;) to different screen sizes.*

 - in a row of three flex items, affix the middle item to the center of the container  (`justify-content: center`) and align the adjacent items to the container edges (`justify-self: flex-start` and `justify-self: flex-end`). 

  *Note that values `space-around` and `space-between` on
   `justify-content` property  will not keep the middle item centered about the container if the adjacent items have different widths.*

&lt;!-- begin snippet: js hide: true console: true babel: false --&gt;

&lt;!-- language: lang-css --&gt;

    #container {
      display: flex;
      justify-content: space-between;
      background-color: lightyellow;
    }
    .box {
      height: 50px;
      width: 75px;
      background-color: springgreen;
    }
    .box1 {
      width: 100px;
    }
    .box3 {
      width: 200px;
    }
    #center {
      text-align: center;
      margin-bottom: 5px;
    }
    #center &gt; span {
      background-color: aqua;
      padding: 2px;
    }

&lt;!-- language: lang-html --&gt;

    &lt;div id=&quot;center&quot;&gt;
      &lt;span&gt;TRUE CENTER&lt;/span&gt;
    &lt;/div&gt;

    &lt;div id=&quot;container&quot;&gt;
      &lt;div class=&quot;box box1&quot;&gt;&lt;/div&gt;
      &lt;div class=&quot;box box2&quot;&gt;&lt;/div&gt;
      &lt;div class=&quot;box box3&quot;&gt;&lt;/div&gt;
    &lt;/div&gt;

    &lt;p&gt;note that the middlebox will only be truly centered if adjacent boxes are equal width&lt;/p&gt;

&lt;!-- end snippet --&gt;

 [jsFiddle version](https://jsfiddle.net/7an37m20/12/)

---

As of this writing, there is no mention of `justify-self` or `justify-items` in the [flexbox spec](https://www.w3.org/TR/css-flexbox-1/).

However, in the [CSS Box Alignment Module](http://www.w3.org/TR/css-align-3/), which is the W3C&#39;s unfinished proposal to establish a common set of alignment properties for use across all box models, there is this:

[![enter image description here][4]][4]
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;sub&gt;Source: [W3C](https://www.w3.org/TR/css3-align/#overview)&lt;/sub&gt;

You&#39;ll notice that `justify-self` and `justify-items` are being considered... *but not for flexbox*.

---

I&#39;ll end by reiterating the main question:

&gt; Why are there no &quot;justify-items&quot; and &quot;justify-self&quot; properties?


  [1]: https://www.w3.org/TR/css-flexbox-1/#overview
  [2]: https://i.stack.imgur.com/9Oxw7.png
  [3]: https://www.w3.org/TR/css-flexbox-1/#box-model
  [4]: https://i.stack.imgur.com/uu2tP.png

In CSS Flexbox, why are there no &quot;justify-items&quot; and &quot;justify-self&quot; properties?

What can service workers do that web workers cannot? Or vice versa?

It seems that web workers are a subset of the functionality of service workers. Is this correct?

What can service workers do that web workers cannot?

Let&#39;s say I have the SVG file:

    &lt;svg width=&quot;1024&quot; height=&quot;768&quot; xmlns=&quot;http://www.w3.org/2000/svg&quot; xmlns:xlink=&quot;http://www.w3.org/1999/xlink&quot;&gt;
    	&lt;text x=&#39;20&#39; y=&#39;60&#39; style=&quot;font-size: 60px&quot;&gt;b&lt;/text&gt;
    	&lt;text x=&#39;100&#39; y=&#39;60&#39; style=&quot;font-size: 60px&quot;&gt;a&lt;/text&gt;
    &lt;/svg&gt;

I want to somehow align the top of `a` and `b`. Actually, I want my positioning to be according to the `roofline` instead of `baseline`!

vertical alignment of text element in SVG

Why don&#39;t we have `box-sizing: margin-box;`? Usually when we put `box-sizing: border-box;` in our style sheets we really mean the former.

&lt;br&gt;
**Example:**

Let&#39;s say I have a 2 column page layout. Both columns have a width of 50%, but they look kind of ugly because there&#39;s no gutter (gap in the middle); Below is the CSS:

	.col2 {
		width: 50%;
		float: left;
	}



&lt;br&gt;To apply a gutter you might think we could just set a right margin on the first of the 2 columns; something like this:

	.col2:first-child {
		margin-right: 24px;
	}

But this would make the second column wrap onto a new line, because the following is true:

	50% + 50% + 24px &gt; 100%

`box-sizing: margin-box;` would solve this issue by including margin in the calculated width of the element. I would find this *very* useful if not more useful than `box-sizing: border-box;`.

CSS3 box-sizing: margin-box; Why not?

If you look at the [CSS box model spec][1], you&#39;ll observe the following:

&gt; The [margin] percentage is calculated with respect to the **width** of the generated box&#39;s containing block. **Note that this is true for &#39;margin-top&#39; and &#39;margin-bottom&#39; as well.** If the containing block&#39;s width depends on this element, then the resulting layout is undefined in CSS 2.1.  *(emphasis mine)*


  [1]: http://www.w3.org/TR/CSS2/box.html#margin-properties

This is indeed true.   But *why*?  What on earth would compel anyone to design it this way?  It&#39;s easy to think of scenarios where you want, e.g. a certain thing to always be 25% down from the top of the page, but it&#39;s hard to come up with any reason why you would want vertical padding to be relative to the horizontal size of the parent.

Here&#39;s an example of the phenomenon I&#39;m referring to:

    &lt;div style=&quot;border: 1px solid red; margin: 0; padding: 0; width: 200px; height: 800px;&quot;&gt;
      This div is 200x800.
      &lt;div style=&quot;border: 1px solid blue; margin: 10% 0 0 10%;&quot;&gt;
        This div has top-margin of 10% and left-margin of 10% with respect to its parent.
      &lt;/div&gt;
    &lt;/div&gt;
http://jsfiddle.net/8JDYD/

Why are margin/padding percentages in CSS always calculated against width?

Is there a W3 or any other noteworthy standard on how to represent a color (including alpha channel) in hex format?

Is it #RGBA or #ARGB?

Hex representation of a color with alpha channel?

What is the easiest way to pretty print (a.k.a. formatted) a `org.w3c.dom.Document` to stdout?

What is the shortest way to pretty print a org.w3c.dom.Document to stdout?

I have a complete XML document in a string and would like a `Document` object. Google turns up all sorts of garbage. What is the simplest solution? (In Java 1.5)

**Solution** Thanks to [Matt McMinn](https://stackoverflow.com/users/1322/matt-mcminn), I have settled on this implementation. It has the right level of input flexibility and exception granularity for me. (It&#39;s good to know if the error came from malformed XML - `SAXException` - or just bad IO - `IOException`.)

    public static org.w3c.dom.Document loadXMLFrom(String xml)
        throws org.xml.sax.SAXException, java.io.IOException {
        return loadXMLFrom(new java.io.ByteArrayInputStream(xml.getBytes()));
    }
    
    public static org.w3c.dom.Document loadXMLFrom(java.io.InputStream is) 
        throws org.xml.sax.SAXException, java.io.IOException {
        javax.xml.parsers.DocumentBuilderFactory factory =
            javax.xml.parsers.DocumentBuilderFactory.newInstance();
        factory.setNamespaceAware(true);
        javax.xml.parsers.DocumentBuilder builder = null;
        try {
            builder = factory.newDocumentBuilder();
        }
        catch (javax.xml.parsers.ParserConfigurationException ex) {
        }  
        org.w3c.dom.Document doc = builder.parse(is);
        is.close();
        return doc;
    }



How do I load an org.w3c.dom.Document from XML in a string?

can use anything in any order? does placing of `&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html;charset=UTF-8&quot;&gt;` is important before `&lt;title&gt;`

this is most used, is it best way?

    &lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.01 Transitional//EN&quot;
            &quot;http://www.w3.org/TR/html4/loose.dtd&quot;&gt;
    
    &lt;html lang=&quot;en&quot;&gt;
    
    &lt;head&gt;
    	&lt;meta http-equiv=&quot;content-type&quot; content=&quot;text/html; charset=utf-8&quot;&gt;
    	&lt;title&gt;Title Goes Here&lt;/title&gt;
        &lt;link rel=&quot;stylesheet&quot; href=&quot;http://sstatic.net/so/all.css?v=5912&quot;&gt;
        &lt;link rel=&quot;shortcut icon&quot; href=&quot;http://sstatic.net/so/favicon.ico&quot;&gt;
         &lt;script type=&quot;text/javascript&quot; src=&quot;http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js&quot;&gt;&lt;/script&gt;
    &lt;script type=&quot;text/javascript&quot;&gt;
        $(function() {
        
            $(&quot;#wmd-input&quot;).focus();
            $(&quot;#title&quot;).focus();
            $(&quot;#revisions-list&quot;).change(function() { window.location = &#39;/posts/1987065/edit/&#39; + $(this).val(); });
        
        });        
    &lt;/script&gt;

    
    &lt;/head&gt;
    
    &lt;body&gt;
    &lt;p&gt;This is my web page&lt;/p&gt;
    
        &lt;script type=&quot;text/javascript&quot; src=&quot;http://ajax.googleapis.com/ajax/libs/mootools.js&quot;&gt;&lt;/script&gt;
    &lt;/body&gt;
    
    &lt;/html&gt;


this site http://stackoverflow.com doesn&#39;t have any encoding and `&lt;meta&gt;`


I use a CMS which has SEO component which adds every `&lt;meta&gt;` for SEO after all js and css. files. can placing of any elements in any order which are allowed in `&lt;head&gt;` affect document compatibility and encoding?

What are best practices to order elements in &lt;head&gt;?

Can a CSS `px` be a fraction? Is it allowed by the standards? And if so, do the major browsers support it?

Let&#39;s back the answers up with documentation, folks.

Can a CSS pixel be a fraction?

The CSS2 box model tells us that [adjoining vertical margins collapse](http://www.w3.org/TR/CSS2/box.html#collapsing-margins).

I find it quite annoying, being the source of many design bugs. I hope that by understanding the purpose of collapsing margins, I will understand when to use them and how to avoid them when they are not needed.

What is the purpose of this feature?


What is the point of CSS collapsing margins?

I&#39;m looking for a tool that will give me the proper generated source including DOM changes made by AJAX requests for input into W3&#39;s validator. I&#39;ve tried the following methods:


 1. 
[Web Developer Toolbar][1] - Generates invalid source according to the doc-type (e.g. it removes the self closing portion of tags). Loses the doctype portion of the page.
 2. [Firebug][2] - Fixes potential flaws in the source (e.g. unclosed tags). Also loses doctype portion of tags and injects the console which itself is invalid HTML.
 3. IE Developer Toolbar - Generates invalid source according to the doc-type (e.g. it makes all tags uppercase, against XHTML spec).
 4. Highlight + View Selection Source - Frequently difficult to get the entire page, also excludes doc-type.

Is there any program or add-on out there that will give me the exact current version of the source, without fixing or changing it in some way? So far, Firebug seems the best, but I worry it may fix some of my mistakes.

**Solution**

It turns out there is no exact solution to what I wanted as Justin explained. The best solution seems to be to validate the source inside of Firebug&#39;s console, even though it will contain some errors caused by Firebug. I&#39;d also like to thank Forgotten Semicolon for explaining why &quot;View Generated Source&quot; doesn&#39;t match the actual source. If I could mark 2 best answers, I would.

  [1]: https://addons.mozilla.org/en-US/firefox/addon/60 &quot;Web Developer Toolbar&quot;
  [2]: https://addons.mozilla.org/en-US/firefox/addon/1843

Best Way to View Generated Source of Webpage?

When using the `xhtml1-transitional.dtd` doctype, collecting a credit card number with the following HTML

    &lt;input type=&quot;text&quot; id=&quot;cardNumber&quot; name=&quot;cardNumber&quot; autocomplete=&#39;off&#39;/&gt;

will flag a warning on the W3C validator:

&gt;there is no attribute &quot;autocomplete&quot;.


Is there a W3C / standards way to disable browser auto-complete on sensitive fields in a form?

Is there a W3C valid way to disable autocomplete in a HTML form?

A relative of mine who started to learn Web Development asked me this question. 

Why `&lt;script src=&quot;min.js&quot;&gt;&lt;/script&gt;` and `&lt;link rel=&quot;stylesheet&quot; href=&quot;min.css&quot;&gt;`? Why not `&lt;style href=&quot;min.css&quot;&gt;&lt;/style&gt;`. Why do we use `link` tag to add external CSS in the page but when we link CSS to page but we use `&lt;style&gt;...&lt;/style&gt;` when we write CSS inside `&lt;head&gt;`?

I told him that it&#39;s because of spec. Is there any more info to give to him?

Why do we use &lt;script&gt; for scripts, but not &lt;style&gt; for external CSS?

I think according to W3 spec, you&#39;re supposed to do

    &lt;input type=&quot;checkbox&quot; checked=&quot;checked&quot; /&gt;

And

     selected=&quot;selected&quot;

But, most browsers will accept it you just write &quot;CHECKED&quot; and don&#39;t give it a value. So, what if you do include the attribute, are there any values that would be (consistently) considered false?

What values for checked and selected are false?

Recently I have come across an issue where I wanted to disable auto-complete in all browsers.

Chrome has a new feature in settings where you can add a card number. And the requirement was to also disable that.

What worked in all browsers was to do this `autocomplete=false` at form level.

But this is not compliant with w3 rules, where they enforce to have `autocomplete=off|on`.

**Can someone please explain to me why `false` works in all browsers?**

even ie8, all firefox, safari etc., but it is not compliant.

Autocomplete off vs false?

MTOM is the W3C Message Transmission Optimization Mechanism, a method of efficiently sending binary data to and from web services.

How does it work in general?

How does MTOM work?

I have a form that has two buttons. One for saving a record and the other for cancelling the save procedure. I am using the `rails.js` *(a common AJAX/jQuery plug-in for those of you not in the know)*  javascript file that works with jQuery for unobtrusive javascript/ajax calls. When I send the form data over ajax, I want the name and value of the button I clicked to be submitted with the rest of the data so that I can make a decision on what to do based on which button was clicked.

The method in the `rails.js` file uses `.serializeArray()` for sending form data to the server. The problem is that this doesn&#39;t include the name/value pair of the button I&#39;ve clicked. jQuery&#39;s website states that they do this on purpose (eventhough its my opinion that they should):

&quot;The `.serializeArray()` method uses the standard W3C rules for [successful controls][1] to determine which elements it should include; in particular the element cannot be disabled and must contain a name attribute. No submit button value is serialized since the form was not submitted using a button.&quot;

How can they assume that a form WASN&#39;T submitted using a button? This makes no sense and a wrong assumption I believe.

Under the W3C rules the button which was activated for the submission of a form is considered a **successful control**.

Since the developers of jQuery have decided to do this on purpose, can I assume that there is another method that **DOESN&#39;T** exclude the activated button in a serialization?

**EDIT: Here is quick example of what my form might look like...**

    &lt;!DOCTYPE html5&gt;
    &lt;html&gt;
    &lt;head&gt;
    &lt;script src=&quot;http://ajax.googleapis.com/ajax/libs/jquery/1.4.3/jquery.min.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;
    &lt;script type=&quot;text/javascript&quot;&gt;
      $(document).ready(function() {
        $(&#39;#form&#39;).submit(function(e) {
          // put your breakpoint here to look at e
          var x = 0;
        });
      });
    &lt;/script&gt;
    &lt;/head&gt;
    &lt;body&gt;
      &lt;form id=&quot;form&quot;&gt;
        &lt;input name=&quot;name&quot; type=&quot;text&quot;&gt;&lt;br/&gt;
        &lt;input name=&quot;commit&quot; type=&quot;submit&quot; value=&quot;Save&quot;/&gt;
        &lt;input name=&quot;commit&quot; type=&quot;submit&quot; value=&quot;Cancel&quot;/&gt;
      &lt;/form&gt;
    &lt;/body&gt;

  [1]: http://www.w3.org/TR/html401/interact/forms.html#h-17.13.2

jQuery serializeArray doesn&#39;t include the submit button that was clicked

I&#39;m in halfway trough an html parser and found html5 defined **explicitly** the rules of thumb for parsing *ill formed html*. *(And I used to infer them from DTDs, sigh)*

I love that fact, but I know well that html5 isn&#39;t finalized yet (also I wonder if it ever will) and that it isn&#39;t developed by the W3C, but by the WHATWG.

Searching for the spec I need I&#39;m presented with:

 * 8.2 section of the **W3C** *TR*  
http://www.w3.org/TR/html5/syntax.html#parsing

or

* 11.2 section of the **WHATWG** *web-apps/current-work*  
http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html

If it wasn&#39;t for the section numbers I would induce those are simply the same. But the different numbering makes me wonder. *Which version is, supposedly, the most authoritative?*

WHATWG seems to have more sections, and to have been *added to* since W3C uploaded its candidate recommendation.

Will W3C update to the WHATWG version?  
Or will they stick to their current candidate until it gets to the official recommendation status?

**Which html5 spec are we poor devils supposed to follow, when in doubt?**

HTML5: W3C vs WHATWG. Which gives the most authoritative spec?

Can we place `&lt;img&gt;` inside `&lt;h1&gt;` according to web standards? like this

    &lt;h1&gt; Demo text &lt;img src=&quot;anyimage.jpg&quot;/&gt; &lt;/h1&gt;

Can we place `&lt;img&gt;` inside `&lt;h1&gt;` according to web standards?

Is this the correct use of `Blockquote`,  `q` and `cite`?

    &lt;p&gt;
    &lt;blockquote&gt;Type HTML in the textarea above, &lt;q&gt;and it will magically appear&lt;/q&gt; in the frame below.
    &lt;/blockquote&gt;
    &lt;cite&gt;&lt;a href=&quot;http://stackoverflow.com&quot;&gt;refrence url&lt;/a&gt;
    &lt;/p&gt;

Is use of `Blockquote`,  `q` semantically correct? or both are presentational element , so should not be used?

Correct use of Blockquote, q and cite?

I wish HTML could do something semantically equivalent to this;

    &lt;dl class=&quot;main-list&quot;&gt;
        &lt;definitionitem&gt;
            &lt;dt&gt;Some Thing&lt;/dt&gt;
                &lt;dd&gt;You know it!&lt;/dd&gt;
            &lt;dt&gt;Another Thing&lt;/dt&gt;
                &lt;dd&gt;Word.&lt;/dd&gt;
        &lt;/definitionitem&gt;
        &lt;definitionitem&gt;
            &lt;dt&gt;Stuff&lt;/dt&gt;
                &lt;dd&gt;Alright!&lt;/dd&gt;
        &lt;/definitionitem&gt;
    &lt;/dl&gt;

However, since the closest I&#39;ve come is something I&#39;m not 100% satisfied with the semantics of;

    &lt;div class=&quot;redundant-wrapper&quot;&gt;
        &lt;dl class=&quot;main-list&quot;&gt;
            &lt;dt&gt;Some Thing&lt;/dt&gt;
                &lt;dd&gt;You know it!&lt;/dd&gt;
            &lt;dt&gt;Another Thing&lt;/dt&gt;
                &lt;dd&gt;Word.&lt;/dd&gt;
        &lt;/dl&gt;
        &lt;dl class=&quot;another-main-list&quot;&gt;
            &lt;dt&gt;Stuff!&lt;/dt&gt;
                &lt;dd&gt;Alright!&lt;/dd&gt;
        &lt;/dl&gt;
    &lt;/div&gt;

I was wondering if anyone has any other ideas of how you might do this?

Also, the reason the items would be grouped is because they are visually grouped in the content that is being marked up. Imagine a dictionary page, with a single definition list, where each definition is in an inset box that is floated left. I run into this situation all the time.

All W3c Solutions on Gang of Coders

Total of 29 W3c Solutions

Can we use any other TAG inside <ul> along with <li>?