Parsoid/Broken wikitext tar pit

From mediawiki.org

This page lists the baddest, hardest and least rewarding broken wikitext snippets we have come across that are really not worth tackling unless you feel very masochistic. Even then, it might actually be a bad idea to tackle this as it would create a lot of implementation complexity for little gain. We also have techniques like selective serialization to hide these issues under the rug. You have been warned!

These snippets might be round-tripped correctly in some cases, but that may just be accidental.

<source> tag used as an extension[edit]

Looks like this is more common than we thought which means we will recognize this as an extension (Bug 47579), but this will current suppress the use of the tag as a HTML5 tag.

‎<source> is now a valid HTML5 tag and as such will not be recognized as an extension. The implication is that, the content found in the source tag will be treated as regular wikitext markup. Please use ‎<syntaxhighlight> as the replacement.

This kind of wikitext markup has been found on the following pages (might have since been edited and fixed):

Missing closing tags[edit]

Missing closing tags will get fixed up the HTML client based on the HTML5 spec. This may not always lead to final HTML that can be round-tripped back to the original source. Parsoid does a lot of work to keep track of auto-inserted or auto-deleted closing tags in many cases and round-trips them correctly, but this may not be possible in all cases (ex: unclosed wikitext-table). In general, it is possible that some wikitext markup with missing closing tags might round-trip back differently than the original.

{|
|-
|foo
|-
|bar
|- |} <!-- Table closing tags have to show up on a new line -->

This kind of wikitext markup has been found on the following pages (might have since been edited and fixed):