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):
<pre> 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
<i>, but not for
<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.)