Hardly a real problem, but maybe a code review reveals more: when using Google Chrome and having unbalanced HTML tags in a post (tags for which no matching opening or closing tag is found) then hitting Ctrl-B or Ctrl-I (or Command-B or Command-I) somewhere in the post, inserts additional brackets.

Like (when not in a code block):

Now hitting Ctrl-B (both below or above the unbalanced tag), gets me:
>**strong text**>
instead of
**strong text**

On my Mac, this only happens in Chrome, not in Safari nor Firefox. It only occurs for allowed tags, like <pre>, <b> or <i>, but not for <u> or <blink>. The toolbar buttons do not get confused. When the unbalanced tags are in code blocks or within backticks, then all is fine too.

(Chrome 9.0.597.107 and 10.0.648.127 on latest OS X.)


1 Answer 1


I missed this one previously. Seems very likely that this is pretty much the same thing as Why am I getting undefined text in the Answer text box?, in which case this shouldn't be happening anymore. I for one can't reproduce it. Can you confirm this is fixed?

  • Seems fine indeed.
    – Arjan
    Commented Aug 9, 2011 at 16:27

You must log in to answer this question.

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