Both @slm and I managed to vote to approve this suggested edit, not realizing it was fixing broken code in the question as opposed to an answer. (Faheem Mitha rejected, after I admitted my mistake in chat and asked for reject votes). Of course, I went ahead and rolled back right after it was approved…
We'd like answers on the site to be free of errors, like the missing $, and to promote best practices, like quoting. So I think we want to continue approving suggested edits similar to that for answers.
However, those mistakes happened to be the problem the OP was experiencing. Fixing the code in the question lead to it being "Hey, why doesn't this [working code] work?", leaving the question useless for the OP, and nonsensical to the rest of us.
It is possible to tell them apart on that screen, by looking at the very bottom, but it's easy to miss. (Examples from SO):
vs. 
AFAIK, the only difference is the light-gray text, hidden at the bottom, saying "answered" or "asked". (I think the line-wrapping difference is only due to the number of tags.)
