<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On 28 May 2014, <br>Hixie wrote:</div><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">You're looking at the W3C fork of the HTML spec.<br><br>The WHATWG standard says:<br><br> Contexts in which this element can be used:<br> Where flow content is expected.<br><br>See:<a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-main-element" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="11">http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-main-element</a><br><br>Differences like this are why I've previously asked the W3C to stop <br>forking the WHATWG specs, but they have so far refused.<br><br>HTH,<br>-- <br>Ian Hickson </span><br></div></div></blockquote><br><div>We understand how you like to rewrite the history of HTML Ian,</div><div><br></div><div>But the <main> element and its definition is not and never has been a fork of the WHATWG spec. Attempting to argue otherwise just makes you look silly. Please remember you don't own HTML.</div><div><br></div><div>Regards</div><div>Stevef</div></body></html>