Bug of not stripped tagI include the bug here in this post (visible in edit)

  • 1
    $\begingroup$ I agree this looks like a bug, but in which situtation do we have < that should not be in code or math environments? Since there is a colorful and helpful box, I don't think newcomers should be too confused. $\endgroup$ – Raphael Jul 4 '16 at 8:52
  • 2
    $\begingroup$ When posting bug reports, it's usually best to include a screenshot so the post can be made sense of later. $\endgroup$ – Raphael Jul 4 '16 at 8:58
  • $\begingroup$ @Raphael I disagree with "support" tag, this is a bug, maybe not that important, but still, what next? $\endgroup$ – Evil Jul 4 '16 at 13:12
  • $\begingroup$ @Oded changed tags which means he as dev on SO's payroll does not think this is a bug. Little to be done. FWIW, since this is documented behaviour I'd agree it's not a bug. If you want it changed, it's a feature request. $\endgroup$ – Raphael Jul 4 '16 at 13:37

< is also the starting character of any HTML tag - which a subset of is allowed in markdown.

As such - it isn't escaped by the parser - and your browser thinks that everthing after < (until a > is reached) is a tag. So isn't shown on the page.

Solution? When posting math, use math formatting, as in the edited post.

  • $\begingroup$ I am rather aware of the HTML, and please take in mind that 'script' tag is stripped away,'a' is stripped, attributes are stripped away, so only usable options are already put in another form to editor and MathJax available, but not existing tags are not stripped although they are parsed anyway. So no benefits but when user comes unaware of that the part of the post just disappears. I was the one who corrected it, so I do not need support - I think this is a bug, like the one with broken MathJax, and MathJax preview in review queue so this is either bug or this post is to be deleted. $\endgroup$ – Evil Jul 4 '16 at 8:29
  • 1
    $\begingroup$ "your browser thinks that everthing after < [...] is a tag. So isn't shown on the page." -- inspecting the page source it's clear that the missing text does not even make it to the browser. It goes missing somewhere in your pipeline. $\endgroup$ – Raphael Jul 4 '16 at 13:38
  • $\begingroup$ Yes, I have checked, @Raphael is right, no sign of it. $\endgroup$ – Evil Jul 4 '16 at 13:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .