So it is a bit more complex than that if they want to enable user markup. https://code.google.com/p/pagedown/source/browse/Markdown.Sa... https://code.google.com/p/pagedown/wiki/PageDown
It is [message] -> [parse] -> [sanitize], generally.
A) It was not as simple as you suggested if there was markup involved in the message.
B) They'd have to use a parser and I linked to a parser that sanitizes that was once used in a pretty big network of sites.
I'm uncertain if you misunderstood or are simply agreeing with me in a tone of writing that makes it sound like you disagree.
The safety of widely-deployed Markdown + sanitizer libraries is largely thanks to testing at scale and a history of patches for XSS vulnerabilities.
While it's still the fastest method for changing the page DOM it shouldn't be. When used outside of user inputted scenarios it's fine.
You need to list what variables are "unsafe", but you don't need to list out the ways they might be unsafe. If it's got the potential to be unsafe, assume it's completely unsafe in every conceivable way, and don't use it in any context apart from as an unsafe text string.
The rookie code is something like:
And agreed. InnerHTML should be removed from browsers.