Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Have a look at this question:

Now hit edit and look at the preview. Doesn't match, does it?

Edit: Yes, I am aware that I didn't close the <pre> tag.

Repro attempt:

{ "name": "Gaming Meta", "logo_url": "", "api_endpoint": "", "site_url": "", "description": "Q&A about the Gaming site", "icon_url": "", "state": "linked_meta", "creation_date": 1279825996, "styling": { "link_color": "#3D3D3D", "tag_foreground_color": "#666666", "tag_background_color": "#FFF" }

Notice the creation_date item.

On IE7 (and IE8's IE7 compatibility mode), this results in author/editor signatures wandering off the right side of the page:

...where gouls devour them...

share|improve this question
Considering closing the <pre> tag gets you the proper display, and that closing your tags is generally a good idea, wouldn't that be a good solution, as opposed to trying to get functionality for syntax you shouldn't be using? – Grace Note Jul 22 '10 at 22:52
@Grace: Well, because people forget and don't notice that they've forgot... like me. – uɐɯsO uɐɥʇɐN Jul 22 '10 at 23:40
@George - Invalid input will, in most situations, yield an undesired result. I have to agree that this isn't a bug, invalid HTML = unpredictable results. – Nick Craver Jul 22 '10 at 23:59
I could consider this a bug if it did something really bad, like corrupt the layout of the page or allowing script injection. But messing up the formatting of the post itself seems about par for the course... – Shog9 Jul 23 '10 at 0:10
@Shog9: It does mess up the layout on IE7 (but not Opera). – mmyers Jul 23 '10 at 0:26
@mmyers: ah, so it does. Poor IE7 users... – Shog9 Jul 23 '10 at 1:50
up vote 1 down vote accepted

What is the point of this request? You didn't close the <pre> tag, so somehow that is our bug?

Are you aware that Markdown is not supported inside HTML blocks? Please read specifically where it says

Markdown can't be used within HTML blocks.

I tested on dev and unclosed <pre> is indeed stripped:

test input:





share|improve this answer
Yes, I am just pointing out how the markdown system degrades when someone inadvertently forgets to close a tag - and doesn't notice it. – uɐɯsO uɐɥʇɐN Jul 23 '10 at 0:06
Maybe some sort of warning message between the edit box and the preview would help with this? – SamB Feb 6 '12 at 22:52

You must log in to answer this question.

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