This might actually be a WONTFIX/INVALID, and just Chrome being bitchy during development..

If someone actually has some advice... As I think it might be bogus, cause I was looking at CR, and that generates a few more, but the syntax looks sane...

And is pointless reporting them if it's just chrome bitching...

which line exactly triggers the error (ie. line 212 in your case) ?

Done from mw.org home page. lines 254-263

<div id="p-search">

<h5 lang='en-gb' dir='ltr'><label for="searchInput">Search</label></h5>
<form action="/w/index.php" id="searchform">
    <input type='hidden' name="title" value="Special:Search"/>
            <div id="simpleSearch">
                    <input id="searchInput" name="search" type="text"  title="Search MediaWiki [f]" accesskey="f"  value="" />
                    <button id="searchButton" type='submit' name='button'  title="Search the pages for this text"><img src="http://bits.wikimedia.org/skins-1.17/vector/images/search-ltr.png?301-2" alt="Search" /></button>
                </div>

MediaWiki:261HTML parse error (recovered gracefully)

</form>

</div>

Line 261 is " </div>"

ie the 2nd closing div from the bottom

Chromium Issue 73703. Seems it gives such errors even for valid pages. They
turned off off all the parse error reporting.

http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/746fabed3eea2bfa/e6bd3e0c49fc857b

(In reply to comment #5)

Chromium Issue 73703. Seems it gives such errors even for valid pages. They
turned off off all the parse error reporting.

http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/746fabed3eea2bfa/e6bd3e0c49fc857b

Cheers :)