what-would-happen-if-i-formatted-an-entire-question-like-this-on-stackoverflow-or-any-other-site-especially-given-that-tags-do-not-support-linebreaks-and-a-reader-will-have-to-side-scroll-just-to-read-the-question-yeah-probably-not-the-best-idea-but-hey-i-could-use-stuff-like-this-for-emphasis

Test to determine if language specifier is case-sensitive for this question

All lowercase:

```lang-python
for i in range(10):
    if i % 2:
        print(i)
```

for i in range(10):
    if i % 2:
        print(i)

All caps:

```LANG-PYTHON
for i in range(10):
    if i % 2:
        print(i)
```

for i in range(10):
    if i % 2:
        print(i)

Language name all caps:

```lang-PYTHON
for i in range(10):
    if i % 2:
        print(i)
```

for i in range(10):
    if i % 2:
        print(i)

All mixed caps:

```LaNg-PyThOn
for i in range(10):
    if i % 2:
        print(i)
```

for i in range(10):
    if i % 2:
        print(i)

Language name mixed caps:

```lang-PyThOn
for i in range(10):
    if i % 2:
        print(i)
```

for i in range(10):
    if i % 2:
        print(i)

http://[::1] works in the preview (and I assume also after submitting the post)

with markdown: http://[::1]

@muru’s space formatting test displays

on my system.

The <ol start> attribute vs. Markdown lists:

1. Item #1
2. Item #2
3. Item #3

2. Item #2
3. Item #3

9. Item #9
10. Item #14

8. Item #8

(Recreation of the example post from this upcoming blockquote change announcement.)

Quotes are cool:

But are they?
How do they work?

Do they work and look good?

What about wtht code
And other stuff?
Seems OK.

That's not bad.

Quotes all the way down? Turtles Should we set a max quote depth?

Actual code above:

>>>>>>> Quotes all the way down?    
>>>>> Turtles    
>>> Should we set a max quote depth?

Now the same thing but with empty lines between each line:

Quotes all the way down?

Turtles

Should we set a max quote depth?

Markdown above:

>>>>>>> Quotes all the way down?   

>>>>> Turtles    

>>> Should we set a max quote depth?

Quoting headers?

Headers?

Quoting?

Quoting headers.

Headers.

Quoting.

What about images:

In the proposed example, this style: outline: 10px solid #ddd; was added to the existing css rule: .post-text blockquote img, .... It's crude, but it provides that much needed border around the image differentiating it from the white background, while also making it obvious that it's part of the quote.

An empty quote block? Nope, that's a spoiler!

There's actually a non-breaking space character in it.

Here's a spoiler block with some text inside:

Gandalf is Magneto!

Both quote blocks above contain only a single line, but notice the height difference because the first one doesn't contain any visible characters.

What about quotes with spoilers?

Quotes?

! With spoilers?

Curiosity killed the cat!

Indeed it does not work if they're on the same level, but works if they spoiler has an extra > relative to the current quote count of >'s.

Quote block with a spoiler block with an image inside:

• List

Unindented snippet

• List

  Indented snippet

  Continuing list's indent level... Things written here fail to render correctly in the preview (show up as code block), but works when posted... Try it by clicking edit

  I suspect that it's because of the _{edit above snippet} button

How CommonMark renders the markdown preview (observed when editing a post) for various Internet top-level domains (TLD)

Bug: meta.so meta.se (reference: https://meta.stackexchange.com/a/349028/241919)

Original top-level domains: example.com example.net example.org example.gov example.edu

Infrastructure top-level domain: example.arpa

Country code top-level domains: example.de example.fr example.us example.so (Somalia) example.se (Sweden)

ICANN-era generic top-level domains: example.academy example.aero example.app example.auto example.blog example.coop

Geographic top-level domains: example.africa example.asia example.paris

Brand top-level domains: example.abc example.bing

Special-Use Domains: example.example example.onion example.test example.local

This is a test of commonmark blockquote

One level

Two Levels

Three Levels

Four levels

WE MUST GO DEEPER! (Seeing if quote levels are cumulative)

Testing code snippet

<!doctype html>
<html>
<head>
<title>HTML Test</title>
<script type="text/javascript">
// Say hello world until the user starts questioning
// the meaningfulness of their existence.
function helloWorld(world) {
  for (var i = 42; --i >= 0;) {
    alert('Hello ' + String(world));
  }
}
</script>
<style type="text/css">
p { color: pink }
b { color: blue }
u { color: "umber" }
</style>
</head>
<body>
<h1>Hello world!</h1>
</body>
</html>

Link just after a special character

REFERENCE:https://meta.stackexchange.com/a/349611/771581

REFERENCE;https://meta.stackexchange.com/a/349611/771581

REFERENCE[https://meta.stackexchange.com/a/349611/771581

REFERENCE%https://meta.stackexchange.com/a/349611/771581

REFERENCE-https://meta.stackexchange.com/a/349611/771581

REFERENCE#https://meta.stackexchange.com/a/349611/771581

REFERENCE&https://meta.stackexchange.com/a/349611/771581

REFERENCE>https://meta.stackexchange.com/a/349611/771581

(Now see the above links in edit preview.)

Link separated from the special character by a space

REFERENCE: https://meta.stackexchange.com/a/349611/771581

Also, this bug seems to be specific with a special character.: REFERENCEhttps://meta.stackexchange.com/a/349611/771581

How I broke this site

Markdown spoiler:

testing spoilers

code spoiler! scroll this way to see:                                                                                                                        SPOILER!!!

→ HTML special characters! ←

→ HTML special characters! ←

The Non-comprehensive Formatting Test

Hello world

Hello world

Hello world

Hello world

Hello world

Hello world

Hello world

ABC

DEF

GHI

JKL

MNO

PQR

STU

VWX

YZ

La

La La La

La La La La La

La La La

La

A B C D E F G

ABCDEFG

{waffles}

ODJIFU(#)RIFU#ORINEJF(HUER#U(WI)~I(!#WEURKJIOK(I)@#O_+ER)FI

Test Magic links:

[meta] – link to the current site's Meta; link text is the site name (e.g. "Meta Super User"). Does nothing if the site doesn't have (or already is) a Meta site.

[main] – like [meta], just the other way around.

[edit] – link to the edit page for the post the comment is on, i.e. /posts/{id}/edit. Link text is "edit" (capitalization is respected).

Help center links. Link text for all of these is "help center": [help] should be obvious. [meta-help] links to "What is meta?" (/help/whats-meta) [help/on-topic] links to "What topics can I ask about here?" (/help/on-topic) [help/dont-ask] links to "What types of questions should I avoid asking?" (/help/dont-ask) [help/behavior] links to "What kind of behavior is expected of users?" (/help/behavior).

[tour] and [meta-tour] – equivalent to the FAQ version, but links to the site's Tour page (resp. the meta site's Tour page). Link text is "tour" (capitalization is respected). Legacy names [about] and [meta-about] are still supported.

[ask] – link to the "How to Ask" page

[answer] – link to the "How to Answer" page.

Links to the front page of Stack Exchange sites (link text is the site name): [so] – link to Stack Overflow [su] – link to Super User [sf] – link to Server Fault [metase]/[meta.se] – link to Meta Stack Exchange [ubuntu.se] – link to Ask Ubuntu [mathoverflow.se] – link to MathOverflow [a51] – link to Area 51 [se] – link to the Stack Exchange Localized Stack Overflow sites can be linked as [es.so] – link to Stack Overflow en español [ja.so] – link to スタック・オーバーフロー [pt.so] – link to Stack Overflow em Português [ru.so] – link to Stack Overflow на русском All other Stack Exchange sites, except Stack Apps: [something.se] – link to something.stackexchange.com, if that site exists. Link text is the site name. [sitename.meta.se] or [meta.sitename.se] – link to a site-specific Meta site. Link text is "Meta ".

[chat] – link to the current site's chat site ne showing a list of active rooms from the referring site), the link text being "{site name} Chat".

On Stack Overflow and localized Stack Overflow sites: [mcve], [reprex], [repro], [mre] and [example] – link to the Minimal Complete & Verifiable Example page for the site.

Tags (these work in questions, answers, comments, and chat, but are not formatted as tags in comments): [Note that if you're on meta, tag-name will still point to the main site. Except on Meta Stack Exchange, which doesn't have a main, tag-name makes no difference from tag-name.] tag-name creates a link to the named tag on the main site. tag-name creates a link to a tag on meta. The text is linked

Supported magic links in chat

In chat, only a limited subset of the magic links listed for comments work, plus one chat-specific magic link.

Chat supports the following magic links: [meta], [main], [ask], [answer], all the links to specific sites, and tag links (with tag formatting). Chat also adds [chat-faq], which results in "chat faq".

The tag magic links work as expected on Stack Overflow Chat and Meta Stack Exchange Chat. However, on Stack Exchange Chat, the chat room in which you use the magic link must be associated with a specific Stack Exchange site, and will take on the formatting of tags on that site.

Testing fairly manual matjax conversion and very makeshift psudocode instructions

REMOVE \begin{equation} \begin{array}{|c|c|c|c|c|c|c|c|c|} \hline

REMOVE

\hline \end{array} \end{equation}

replace \n with \n| SPACE replace & with SPACE SPACE | SPACE replace \ with SPACE SPACE |

CLEAN UP TITLE BAR

Remove

\operatorname{

remove |text{Input}

remove }

Unicode subscripts ₁₂₃₄₅₆₇₈₉₀

add header

Testing leading spaces: false false

` false` <code> false</code>

Without custom CSS:

Didn't think my previous answer could fit some more stuff, soooooooooo... Hmm... Hmm...

Apparently tag ending for <kbd> is strange.

something Interesting...

Heh.

my code

spoiler

heh.

Looks like, at some point in the last 3 months, all 4 Markdown language hints were made equivalent.
Previously, the first (lang-markdown) highlighted differently than the other 3, but all 4 look just like the first now.

Markdown highlighting test:

lang-markdown

# Sample Output

heading
--

another heading
==

> quote text

`code text`

_italic_ *italic*

__bold__ **bold**

***bold AND italic***

lang-md/ lang-mkdown/ lang-mkd

# Sample Output

heading
--

another heading
==

> quote text

`code text`

_italic_ *italic*

__bold__ **bold**

***bold AND italic***

This heading was added to test if the IDs assigned to headings change

It looks like H4, H5, and H6 elements were added to the CSS. This is to test to see if they are live on the site for user contributions.

Using Markdown:

An H1 (Markdown)

An H2 (Markdown)

An H3 (Markdown)

An H4 (Markdown)

An H5 (Markdown)

An H6 (Markdown)

Using HTML:

An H1 (HTML)

An H2 (HTML)

An H3 (HTML)

An H4 (HTML)

An H5 (HTML)

An H6 (HTML)

Using HTML with an id attribute (expected to be stripped):

An H1 (HTML)

An H2 (HTML)

An H3 (HTML)

An H4 (HTML)

An H5 (HTML)

An H6 (HTML)

More testing for automatic generation of id and static assignment.

1. Fun with lists and headings:

   1. Issue 1: This is an h5 in a ordered list

   2. Issue 2: This is an h5 in a ordered list

   3. Issue 3: This is an h5 in a ordered list

2. This is the same thing in HTML:

   1. Issue 1 (HTML):

   2. Issue 2 (HTML):

   3. Issue 3 (HTML):

3. HTML with a static id attribute for each <h5>:

   In the preview rendering, the <h5> elements are stripped, but content is displayed.

   1. Issue 1 (HTML with static ID):

   2. Issue 2 (HTML with static ID):

   3. Issue 3 (HTML with static ID):

Test using <!-- language: lang-none --> (i.e. should NOT have syntax highlighting)

Where indicated, the following sections are separately preceded by a line which contains <!-- language: lang-none -->, which should still prevent application of syntax highlighting. Note that using HTML comments to apply code formatting is deprecated.

In code fences

With <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

Without <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

Using 4 space indent

With <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

Without <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

In HTML <pre><code>

With <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

Without <!-- language: lang-none -->

var parent=document.getElementById('parent');
var child=document.getElementById('child');
var preventChild=document.getElementById('preventChild');

All of the above function as expected in the preview below the text input while editing.

Hmm, does pipenv --support (or similarly styled support config dump) work well in a question or answer? Let's find out (edited some content out for size).

Notice the <details><summary>heading</summary>...</details> used to obtain collapsed-by-default section in, e.g., GitHub issues doesn't work here:

Pipenv version: '2018.11.26'

Pipenv location: '/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv'

Python location: '/usr/local/Cellar/pipenv/2018.11.26_2/libexec/bin/python3.7'

Python installations found:

• 3.7.2: /usr/local/bin/python3
• 3.7.2: /usr/local/bin/python3.7m
• 2.7.16: /usr/local/bin/python
• 2.7.16: /usr/local/bin/pythonw
• 2.7.10: /usr/bin/python
• 2.7.10: /usr/bin/pythonw
• 2.7.10: /usr/bin/python2.7

PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '3.7.2',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '18.2.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST '
                     '2018; root:xnu-4903.241.1~1/RELEASE_X86_64',
 'python_full_version': '3.7.2',
 'python_version': '3.7',
 'sys_platform': 'darwin'}

System environment variables:

• PATH
• TERM_PROGRAM
• PIP_REQUIRE_VIRTUALENV
• SHELL
• TERM
• PIP_PYTHON_PATH
• etc.

Pipenv–specific environment variables:

• PIPENV_ACTIVE: 1

Contents of Pipfile ('/Users/[redacted]/Pipfile'):

[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
boto3 = "*"
requests = "*"
six = "*"

[requires]
python_version = "3.6"

Contents of Pipfile.lock ('/Users/[redacted]/Pipfile.lock'):

{
    "[redacted]": ["snip"]
}

public class Hello {
    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

… and then presumably one could continue after the diagnostics.

Well, there’s table support now, so…

Markdown

Minimal Markdown of a table, working both in the preview and the post:

||
|-|

Minimal Markdown of a table, working in the preview, but not in the post:

|
-

|

Minimal Markdown of a table, working in the post, but not in the preview:

||
||

These Markdown snippets don’t render at all in a post, but still produce tables in the preview:

|
-|

|
|-|

This Markdown doesn’t render at all in a post, and doesn’t produce a table in the preview:

|
||

Backslashes, HTML, other random stuff

test|ßßßstatus-completed\ẞ|
\

Line Separator and Paragraph Separator

These don’t seem to separate table rows.

|dgfg|adasd|
|---|:--|
|234234|23|

|dgfg|adasd|
|---|:--|
|234234|23|

Stack Snippets

When editing, the “edit the above snippet” link appears inside the table header.

console.log();

Test

console.log();

Test

This is a test of a malformed link. Something similar was posted and detected by SmokeDetector, but deleted before I was able to see it on the SE site where it was posted.<a href="This is just to verify what SE does wrt. stripping the ">malformed tag. I believe I know what SE will do, but I want to double-check.

Additional test (currently Chrome only, if working):

IIRC, the last time I tested this the backend Markdown->HTML render broke this. It does appear to be working in the edit preview.

This is a link to a question which should highlight some text in Chrome.

Eye in the pyramid

Psych!

red color markdown text
yellow color markdown text

Test—will this render? Typed in visual editor.

"Quote," quoth the quoted.

_{Small text, chapter 4: "Fancy quote formatting" (2008–2022)}

Testing a thing with the new editor.

Here's a footnote link to Google

And a [bracket test].

Testing unicode magic:

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- end snippet​ -->

Testing escapes:

*(\*)[12]*

(*)[12]

Code in spoilers:

>! <pre><code>
>! if True: 
>!     print "Hello World!"
>! </code></pre>

 if True:
     print "Hello World!"
 

vs.

>! ```
>! if True: 
>!     print "Hello World!"
>! ```

! if True: ! print "Hello World!" !

Placeholder 4️⃣ some tests…

text

text

Testing backslash:

@backslash not showing, right?

Code:

\@backslash not showing, right?

https://www.example.com

Let's upload a small image and see if it gets bigger:

Original image is 288x268 pixels.