Backticked code blocks inside spoilers are almost completely illegible on beta sites:
121938
It doesn't reproduce on Meta, but it will on any beta site.  To see an example, check out :        Edit:  I noticed that on SciFi, English, Area 51, and Electrical Engineering (at least - those are the only ones I've tried), spoilers with monospace will show the monospace part whether or not the mouse is hovering over the block (though the normal font will continue to operate normally).  On those sites, however, it hasn't yet joined the Dark Side.
64117
For example,  edit was proposed to an answer to my question. The bug is I see the checkmark when I go to this edit (I can't click checkmark however).
13695
If I try to put something like this into a question or answer  &lt;!-- &lt;br&gt;s are important here --&gt;   the first &gt; after the "br" is matched to the first &lt; before the "!--", resulting in this being displayed:     s are important here -->   This happens in both previews and actual posts. I'd say it's a bug.  HTML comments shouldn't be treated as regular HTML tags; &lt;!-- should only be matched to --&gt;.
16238
How do I escape a backtick ` within a code block?  This is probably a duplicate, since I'm sure it's a common concern, but I can't find a question that addresses this specifically.  How do I write List'1 with the "1" character still in the code-text format?
20141
Padding is missing under the &quot;Communities&quot; border line, and the list is also showing &quot;Communities (0)&quot; (maybe the reason is due to caching as it shows 0 Communities):  Generally, padding is present:
70808
This occurs in the  released recently to the public. When someone posts a code block in their question or answer, the code block is cut off on the right hand side, and I can't scroll to the right to view the rest of it. How can I view these code blocks?
59449
TeX rendering is broken on sites like Math and Physics when viewed over SSL.  For example:  :    And
34326
I've noticed that the background text "Type a tag" at the bottom of the "Ask Question" page is cut off:        Reproduced in Microsoft Edge.
38266
I just approved several edits from a user adding  to questions with the  tag. Apparently , Google Code Prettify has added support for Dart.  I suggest it's time to follow suit and update the default syntax highlighting associated with the  tag. Adding it manually to every question sounds like way too much work, even if I all I have to do is click the "Approve" button.
15175
(This is mainly for Stack Overflow, I did personally not check out color schemes on the other sites. But a  has been raised for beta sites.)  I don't think the current style for visited links on Stack Overflow posts is very nice. The text is black and links are #4A6B82 which looks almost like black or a very dark grey on my screen. That's not very accessible (and that's in spite of my good eyesight).  Additionally, links in inline code sections do not get underlined on hover, which makes them even harder to spot. Sometimes I link to documentation by putting a link on (&lt;- like this), and it is very hard to notice that it is even there (apparently, Meta has the same problem…).  I would find brighter links and consistent underlining very helpful.  I'll tag this as [bug] because I think link coloring is actually broken. And the other choices ([feature-request] [discussion] [support]) don't really fit.
31007
Help!!!  I don't know quite what happened, I was getting frustrated, trying to somehow escape the backticks inside the code formatting. I clicked the edit button too many times, and then the above happened. Perhaps I clicked it to fast, I don't know, but I then got lots of boxes.    Edit:  Based on a test case below, the problem is simply caused by pressing edit while you still have an edit box open. They all go away when you press cancel anywhere once. This makes it much easier to reproduce, and, while not very important, perhaps still something to be fixed.  Note on the pattern:  When you click the first time, you get one box, as normal. When you click again, you get one extra empty box at the top, and another normal box above that. At each click, one empty box is added per existing normal boxes, plus one normal box. What is going on?
74302
When a spoiler blockquote contains text, the text transitions in smoothly using a CSS transition. If it contains an image, the transition is abrupt.    If the CSS were changed from:  .spoiler:hover img {     visibility: visible; } .spoiler img {     visibility: hidden; }   to:  .spoiler:hover img {     opacity: 1; } .spoiler img {     opacity: 0;     transition: opacity 0.5s ease-in; }   .  Live example:      this is a test this is only a test
97909
In the question , I used the &gt;! syntax to create a spoiler section, but it shows up as a normal blockquote with a ! at its start.
99122
I just posted an answer twice (in two different versions) after I got the footer as displayed in the screenshot:    Could you please fix this? (I'm part of the beta, but this is since last year I guess)
120873
I don't know how long this has been happening, but I recently noticed what seems to be a regression: after clicking the "An edit has been made to this post" banner that appears when a question or an answer has been edited while you're viewing it, any code syntax highlighting or math formatting in the post fails to render.  Steps to reproduce:   Open a question with highlighted code or MathJax markup that is likely to get edited soon. (The  or  is a good place to find some.) Leave the question open until someone edits it and the "An edit has been made to this post" banner appears. (For efficiency, open several questions in separate tabs and wait a few minutes until one of them gets edited.) Click the banner. Observe that the question gets reloaded, but it loses any syntax highlighting or math formatting.   (The bug also occurs for edited answers, but those tend to be harder to find on demand.  Unfortunately, editing a post yourself while having it open in another tab doesn't seem to work, since the banner never appears in that case.)    FWIW, the cause of this bug appears to be a missing call to styleCode() (or equivalent code) in the reloadPosts function in realtime-se.js, as included in the  bundle. (In particular, running styleCode() from the browser JavaScript console after reloading the post restores the missing syntax highlighting.)  I'm pretty sure this used to work automatically, so I suspect this is a regression caused by some recent code reorganization.
82402
Notes:  Answers will occasionally be moved to the  when there are too many of them. When using them to report bugs, keep an eye on the post.    This site, Meta Stack Exchange, is usually used as a &quot;test bed&quot; for pending changes happening to the way text is rendered on all network sites. Changes to text rendering that are going to be rolled out to the network are usually deployed here first to test them out and fix any potential glitches. Currently, there are no such changes pending, but if there were, keep in mind that text posted here may render differently from the other sites until the changes roll out to them as well.    As per Jeff's suggestion in : You can use this question as a formatting sandbox. You can:  edit  itself ( questions such as this one require only 100 reputation to edit instead of 2,000) post answers to this question (This question might be , requiring earning 10 reputation on this site to answer) post comments to this question or its answers test suspected bugs with the editor or the rendering post ponies (only when mods are asleep)   Beware that since the  in December 2010, and  added in March 2011, no syntax highlighting is applied unless the question's tags or an inline hint enable it. So, to test highlighting here in the sandbox:  , you can use GitHub-flavor fenced code blocks in your posts, specifying the language after the opening fence: ```html While not hinted otherwise: &lt;html&gt;&lt;/html&gt; source &lt;b&gt;goes&lt;/b&gt; &quot;here&quot;. ```  ```js var a = 3; while (not (a &gt; 0)) {     alert(&quot;JavaScript code &lt;b&gt;goes&lt;/b&gt; here.&quot;); } ```   Or:  Create code blocks in any way (using the fence notation above, the four-space indent form, or using HTML &lt;pre&gt;&lt;code&gt; tags).  Save your post.  Use your browser's developer tools to edit the resulting HTML. To open developer tools, press F12, or ⌥⌘ I on Mac.  Find the &lt;pre&gt; element and add the attribute class=&quot;prettyprint&quot;, or change it into one of the valid syntax hints linked above, like class=&quot;lang-vb prettyprint&quot;.  Run the following in the location bar: javascript:prettyPrint(); or prettyPrint() in the console.     Answers that are considered annoying or obnoxious, or that cause breakage for users, will be deleted. This is .
14156
The link button in the post editor incorrectly escapes square brackets in inline code.  To reproduce:   Write the following MarkDown in the editor  text text `function[]` text text  Select `function[]`, press the link button (), and enter some link the result will be [`function\[\]`][1] which renders as function\[\]   This comes up very often in   when I'm linking to the documentation because the usual way to indicate that a symbol is a function in Mathematica is adding [] after it.  This is a minor thing, as it's easy to manually remove the backslashes, but it's somewhat annoying so I thought I'd mention it.    Edit by Mr.Wizard It is September 2013 and this still hasn't been fixed.  While "adding [] after it" is not presently the custom on Mathematica.SE this is still a bug and still needs to be fixed.