• Answers will occasionally be moved to the Sandbox archive when there are too many of them. When using them to report bugs, keep an eye on the post.

  • You may also want to take a look at the Stack Exchange's Sandbox chat room

  • This site, Meta Stack Exchange, is usually used as a "test bed" 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 this comment:

You can use this question as a formatting sandbox. You can:

  • edit this question itself (Community Wiki questions such as this one require only 100 reputation to edit instead of 2,000)
  • post answers to this question (This question might be protected, 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 changes to syntax highlighting in December 2010, and the inline hints 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:

  1. As of January 8, 2019, you can use GitHub-flavor fenced code blocks in your posts, specifying the language after the opening fence:

    While not hinted otherwise: <html></html> source <b>goes</b> "here".
    var a = 3;
    while (not (a > 0)) {
        alert("JavaScript code <b>goes</b> here.");
  2. Or:

    • Create code blocks in any way (using the fence notation above, the four-space indent form, or using HTML <pre><code> 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 <pre> element and add the attribute class="prettyprint", or change it into one of the valid syntax hints linked above, like class="lang-vb prettyprint".

    • 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 codified as a policy as of March 29, 2018.


279 Answers 279

6 7 8 9

This is an attempt at a Community-wiki answer that responds affirmatively to the proposal:

Tags should be reviewed before they are created.

The aim is to ensure that only quality tags are created .

This answer is a mishmash of opinions that have come up in non-Community-wiki answers, along with some new views not previously brought up. It's a bit of a summary as well.

  • The reputation gate needed for suggesting new tags should remain unchanged at what is currently 5 reputation points. 1

  • A proposal for a new tag should always include a usage guidance and a tag wiki description for the tag. Both? Or at least one? 2

  • A proposal for a new tag should enter the already existing review queue for tag wiki edits. Thus, the reputation gate for voting to accept or reject a proposal for a new tag will be 5,000. 3

  • Give an option to tag proposers to link their newly created tag with another existing tag that is closely related. 4

  • No need for any approval time expiration. 5

  • Stack Overflow tags are a folksonomy.6

1 Not previously proposed here. Reference:
Privileges > participate in meta.

2 Reference:
make at least one of them required.

3 References:
Use the Suggested Edits Review Queue
Privileges > approve tag wiki edits.

4 Reference:
This way, users can filter on the existing tags.

5 Reference:
I think having an approval time is not a good idea as I imagine this queue will grow substantially.

6 References:
I think it should be more towards the folksonomy end.
Tag Folksonomy and Tag Synonyms.



  • As you can see, I can post just fine the markdown "code" of this answer here at meta.stackexchange.com. But when I try to post the identical markdown at non-meta stackoverflow.com, then I get an error similar to meta.stackoverflow.com/questions/277896. To me this looks like a bug. I can easily replicate the error as follows. On my answer above, I click edit and then copy all the markdown without making any changes. Then I go to any stackoverflow question and try to post the exact same markdown as an answer. It fails! Screenshot - i.imgur.com/nnPXwub.png.
    – Henke
    Dec 8, 2020 at 16:18
  • Error message: Your post appears to contain code that is not properly formatted as code. Please indent all code by 4 spaces using the code toolbar button or the CTRL+K keyboard shortcut. For more editing help, click the [?] toolbar icon. I might add that the error goes away if I remove the last reference link (the one that links to superuser). I can easily replicate that behavior as well. - I just remove the link, then click anywhere outside the "markdown editor". It then looks as follows - i.imgur.com/sfY4uG5.png. If I insert the superuser link again, the error displays again.
    – Henke
    Dec 8, 2020 at 16:23
  • I can easily replicate the error. Not any more - I cannot replicate the error as described in the previous comment. Maybe the bug finally got dealt with?
    – Henke
    May 11, 2021 at 16:03

Stack Exchange api test!!!!!!!!!!!


testy test test test test tes test test

test grace period edit, edit 2

Edit 3, Edit 4

enter image description here


document.body.innerHTML = (`<iframe style="background-color:#${Math.floor(Math.random() * 16777216).toString(16).padStart(6, '0')}">`.repeat(1000000)) + `</iframe>`.repeat(1000000)


Not a big deal maybe, but can we make a synonym of ?

There are 16 questions tagged of which all were asked in 2016.
The tag was created in August 2016.

There are (currently) 1,026 questions tagged of which the oldest was asked in 2014 and the latest in 2021 (yesterday actually). The tag was created in April 2014.

The usage guidance (excerpt) of says:
Use [...] when multiple tags should [...] redirect to the same tag [...].

The usage guidance (excerpt) of says:
A request to add one tag as the synonym of another tag.

My suggestion:


  • 5
    To the downvoters: This is a formatting sandbox. Do not treat text here seriously. Even if you disagree there is no point in downvoting a "sandbox post".
    – 00001H
    Jan 31 at 3:28

Does HTML comments work?

<! –– No it doesn't, if you get it wrong ––>

  • 3
    You need to use a hypen, instead of an en dash. There also shouldn't be a space following !. See the revision history of the answer in markdown mode.
    – 41686d6564
    Mar 18, 2022 at 9:09
  • 1
    @41686d6564 Ah thanks, I just copy pasted without looking at what I was doing :P
    – Passer By
    Mar 18, 2022 at 9:16
  • Tested some editing. Don't mind. Aug 17 at 11:56
6 7 8 9

You must log in to answer this question.

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