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

On a recent post of mine I included a code block that was formatted correctly in the preview, but was rendered as regular text after I had to go through the human verification screen. Can this be fixed?

Here's the post where I saw it:

It's been modified since then to add the formatting back in.

share|improve this question
Did you type the captcha words correctly the first time, or did it give you a new set of words? I thought I might have had an issue one time when I failed the test. – Jon Seigel Jun 2 '10 at 13:17
No, I typed them in correctly the first time. – adam0101 Jun 3 '10 at 14:26

Testing this bug.

Code snippet with tab (\t) character

Trucks Compacts SUVs Ford Toyota Honda

Code snippet with 4 spaces

<input type="hidden" name="parameters[0].Key" value="Category" />
<select name="parameters[0].Value">
    <option value="Trucks">Trucks</option>
    <option value="Compacts">Compacts</option>
    <option value="SUVs">SUVs</option>
<input type="hidden" name="parameters[1].Key" value="Manufacturer" />
<select name="parameters[1].Value">
    <option value="Ford">Ford</option>
    <option value="Toyota">Toyota</option>
    <option value="Honda">Honda</option>
share|improve this answer
It would seem the bug is limited to only tab characters preceding code blocks, not 4 spaces. The post above was correctly formatted initially, but after two edits and a human verification form it now looks like that. – Nathan Taylor Jul 14 '10 at 17:46

Thanks to Nathan's repro steps, we were able to find the issue. This will be fixed in the next build.

Edit: We have rolled back this fix, since it may be causing some other issues, so we have to investigate a little further.

Edit 2: After a few changes, we have reenabled this a few days ago and not seen any issues since. So – all good now; this is fixed.

On a personal note, let me add that

tabs are evil.


share|improve this answer
Okay, you want us to vote for that statement on tabs, right? – Arjan Feb 2 '11 at 14:21
Tabs are not evil. It's the mix of tabs and spaces that is evil. I can't stand spaces, myself. – zanlok Feb 2 '11 at 14:42
If the world would use elastic tabstops, then it would be a better place. Lacking this, for the past decade, I've advocated 1TBS and tabs-then-spaces for other content after the first non-tab character. – zanlok Feb 2 '11 at 14:45
As much as I've always detested aligned variables and comments (and hence never had a need for inline tabs, but still love tabs at the start of a line), that elastic tabstops demo is great, @zanlock! – Arjan Feb 2 '11 at 14:48
(He, my comment upvote went to the wrong comment, which I did not even see previously!) – Arjan Feb 2 '11 at 14:49
@Arjan: Huh? I only see one comment upvote, and the only comment before that is yours -- so you must have seen it, if you clicked upvote on anything? – balpha Feb 2 '11 at 15:22
I really think I upvoted a comment about the elastic tabs. Maybe @zanlok moved that text the the 3rd comment? Anyway, I doubt it's a bug: it's either caused by editing, or I'm simply imagining things — just like you are imagining tabs are evil! ;-) – Arjan Feb 2 '11 at 15:25
Sorry guys. I split the comment up so that the two separate ideas were represented on their own merit. Glad to see someone else has heard of elastic tabstops :) – zanlok Feb 2 '11 at 15:45

You must log in to answer this question.

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