Does anyone know how is Doctype versioning going to work with W3Cs snapshoting of the living standard? Or are browsers just going to ignore W3C and stick to implementing WHATWGs spec?
No browser ever paid any attention to the version of the HTML specified. The only use for DOCTYPE—and the reason it remains in HTML5—is "doctype switching", i.e. different rendering modes are triggered in the browsers. You can use "html", "html5", "html6.2" or "foobarbaz" as your doctype, the effect will be the same—they will all trigger standards compliant mode.
>'You can use "html", "html5", "html6.2" or "foobarbaz" as your doctype, the effect will be the same—they will all trigger standards compliant mode.' //
You're wrong if your asserting that any doctype produces the same results globally but it probably doesn't matter unless you're targeting legacy UA.
Maybe but if you use real DOCTYPE such as <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> then you will see huge difference in rendering.
