This is way off topic, but I want to share since I just learned about this a day or two ago. Skip over this comment if you don't care about HTML5 trivia.
I had no idea what this was supposed to be, and I thought maybe it just wasn't loading more content, so I checked the source. While there, Firefox told me there was an error with the HTML, and that the <section> element contained elements that hadn't been properly closed.
This turned out to be because of the first <div> element in the section, because it's trying to be a self-closing element when such a thing isn't possible.
As it turns out, the slashes you see in such elements as <br /> are purely decoration in HTML5. They're a holdover for people like me, who like the structure that XHTML tried to bring to the language. <br> is the proper HTML5 element, and <br /> is just there for decoration/compatibility. The slash doesn't mark the element as void - the element is void regardless of whether or not you use the slash.
The impact of this is that trying to create a self-closing <div> in HTML5 by including the slash in the start tag - i.e. <div /> - only opens a <div> without closing it. You need to include a closing tag right after the opening tag to get the result you want - i.e. <div></div>.
The HTML5 spec [1] covers this nicely: "[I]f the element is one of the void elements, or if the element is a foreign element, then there may be a single U+002F SOLIDUS character (/). This character has no effect on void elements, but on foreign elements it marks the start tag as self-closing." Furthermore, the space before the slash is only necessary for XHTML [2].
That's not what foreign elements are. If you click the link to "foreign elements" in your first link, you'll see that the spec[1] defines foreign elements as "Elements from the MathML namespace and the SVG namespace." In other words, elements which are foreign to HTML.
The <div> element is a "normal element", and the spec doesn't seem to indicate what to do with the slash/solidus on normal elements, only on void or foreign ones.
I got my information for my previous comment from an answer on StackOverflow[2], but the w3c's validator seems to back it up. The OP has been changed to use the explicit close tag on that element, so you'll have to edit the source to use the (non-)self-closing version to check it yourself, but it kicked up errors for me.
Specifically, the error given read "Self-closing syntax (/>) used on a non-void HTML element. Ignoring the slash and treating as a start tag." This is what I said in my previous comment, albeit much more succinctly.
As for your second comment, regarding the space before the slash, I don't understand its relevance to my comment. I said nothing about the space in the element; I only referred to the effect of the slash. Also, you're talking about XHTML, and linking to its spec, in a discussion regarding HTML5. If I'm missing your point, please clarify.
I linked to the HTML spec because it explains that the slash only means something for void or foreign elements. The <div> element is neither, so the slash is either interpreted as an attribute or ignored. You are correct, both in this comment and the previous one; I was agreeing with you and providing sources.
My comment about the spaces was trivia on top of your trivia. I thought it was relevant because all of your examples of self-closing tags had a space.
Type some text over 'chairs' and it will give you an image plus some more text. I think this is supposed to be a parody of a commercial FB ran a little while back, where they compared chairs to facebook.
I actually kind of wonder how they did it, the images are (mostly) accurate. Maybe a google image search?
I had no idea what this was supposed to be, and I thought maybe it just wasn't loading more content, so I checked the source. While there, Firefox told me there was an error with the HTML, and that the <section> element contained elements that hadn't been properly closed.
This turned out to be because of the first <div> element in the section, because it's trying to be a self-closing element when such a thing isn't possible.
As it turns out, the slashes you see in such elements as <br /> are purely decoration in HTML5. They're a holdover for people like me, who like the structure that XHTML tried to bring to the language. <br> is the proper HTML5 element, and <br /> is just there for decoration/compatibility. The slash doesn't mark the element as void - the element is void regardless of whether or not you use the slash.
The impact of this is that trying to create a self-closing <div> in HTML5 by including the slash in the start tag - i.e. <div /> - only opens a <div> without closing it. You need to include a closing tag right after the opening tag to get the result you want - i.e. <div></div>.