Google uses some clever trick to hide the closing tags in your browser. Download the file and open it in your editor of choice, the closing tags are there.
well no, the browser adds them when it loads and parses it for rendering. the inspector just shows you what the browser created. the same is true for all browsers, their inspectors will reveal how the DOM looks like for the browser.
If we're discussing semantics here, when a browser parses it for rendering what would it mean to "add them?" After all, the HTML is only a textual representation of the rendered DOM tree. I think it's perfectly valid to say the inspector is adding them in, since the browser doesn't really bother to adjust the HTML if it can already parse it.
In the talk, he explains that all this is valid HTML5. You don't need quotes, you don't generally need closing tags. Whether you choose to them depends on how dirty it makes you feel, but few browsers will actually care.
A separate but related lesson is that Google cares a ton about performance, so you'll often find these byte-saving tricks in high-traffic Google pages. e.g. the use of "//foo.com" instead of "http://foo.com.
that's not bytesaving, that's called protocol relative URLs, meaning if the linking page is https, //foo.com will be loaded as https://foo.com. most google properties have https modes, this is a way to reduce the complexity of the page and whatever generates the html code.
9 comments
[ 2.9 ms ] story [ 34.0 ms ] threadhttp://i.imgur.com/vCyrY.png
EDIT: Or chrome is auto-adding the tags? As mentioned below curl doesn't replicate the same results, nor does Firefox.
In the talk, he explains that all this is valid HTML5. You don't need quotes, you don't generally need closing tags. Whether you choose to them depends on how dirty it makes you feel, but few browsers will actually care.
A separate but related lesson is that Google cares a ton about performance, so you'll often find these byte-saving tricks in high-traffic Google pages. e.g. the use of "//foo.com" instead of "http://foo.com.