Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/zerver/tests/fixtures/markdown_test_cases.json

1060 lines
90 KiB
JSON
Raw Normal View History

Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"regular_tests": [
{
"name": "codeblock_hilite",
Tolerate spaces after language in markdown fences. See #2357. We now support `~~~ .py ` with that trailing space. Note that the test coverage is Python-side only due to bugdown_matches_marked being set to false, since we don't yet support language syntax on the client side. (imported from commit ccd5fcb0eee01478d349161400103480678d7486)
2014-03-06 00:05:49 +01:00
"input": "Hamlet said:\n~~~~.python \ndef speak(self):\n x = 1\n~~~~",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<p>Hamlet said:</p>\n<div class=\"codehilite\"><pre><span></span><span class=\"k\">def</span> <span class=\"nf\">speak</span><span class=\"p\">(</span><span class=\"bp\">self</span><span class=\"p\">):</span>\n <span class=\"n\">x</span> <span class=\"o\">=</span> <span class=\"mi\">1</span>\n</pre></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"marked_expected_output": "<p>Hamlet said:</p>\n<div class=\"codehilite\"><pre><span></span>def speak(self):\n x = 1\n</pre></div>",
"text_content": "Hamlet said:\ndef speak(self):\n x = 1\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "basic_paragraph",
"input": "test_input",
"expected_output": "<p>test_input</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "test_input"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "codeblock_multiline",
"input": "Hamlet once said\n~~~~\ndef func():\n x = 1\n\n y = 2\n\n z = 3\n~~~~\nAnd all was good.",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<p>Hamlet once said</p>\n<div class=\"codehilite\"><pre><span></span>def func():\n x = 1\n\n y = 2\n\n z = 3\n</pre></div>\n\n\n<p>And all was good.</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Hamlet once said\ndef func():\n x = 1\n\n y = 2\n\n z = 3\n\n\n\nAnd all was good."
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
{
"name": "test",
"input": "it's lunch time",
"expected_output": "<p>it's lunch time</p>"
},
bugdown: Remove trailing whitespace on fence code blocks. This fixes fenced code blocks that are copy-pasted from certain clients having trailing whitespace anoyingly often. Fixes #3998.
2017-03-20 18:54:00 +01:00
{
"name": "codeblock_trailing_whitespace",
"input": "Hamlet once said\n~~~~\ndef func():\n x = 1\n\n y = 2\t\t\n\n z = 3 \n~~~~\nAnd all was good.",
"expected_output": "<p>Hamlet once said</p>\n<div class=\"codehilite\"><pre><span></span>def func():\n x = 1\n\n y = 2\n\n z = 3\n</pre></div>\n\n\n<p>And all was good.</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Hamlet once said\ndef func():\n x = 1\n\n y = 2\n\n z = 3\n\n\n\nAnd all was good."
bugdown: Remove trailing whitespace on fence code blocks. This fixes fenced code blocks that are copy-pasted from certain clients having trailing whitespace anoyingly often. Fixes #3998.
2017-03-20 18:54:00 +01:00
},
bugdown: Remove whitespace strip from inline code. Fixes #4507
2017-11-22 02:27:19 +01:00
{
"name": "inline_code_spaces",
"input": "` outer ` ``` space ```",
"expected_output": "<p><code> outer </code> <code> space </code></p>",
"text_content": " outer space "
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "codeblock_backticks",
"input": "\n```\nfenced code\n```\n\n```inline code```\n",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<div class=\"codehilite\"><pre><span></span>fenced code\n</pre></div>\n\n\n<p><code>inline code</code></p>",
tests: Change test_content to text_content in markdown_test_cases. docs: Fix error in markdown documentation.
2017-10-31 10:30:24 +01:00
"text_content": "fenced code\n\n\n\ninline code"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "hanging_multi_codeblock",
"input": "Hamlet said:\n~~~~\ndef speak(self):\n x = 1\n# Comment to make this code block longer to test Trac #1162\n~~~~\n\nThen he mentioned ````y = 4 + x**2```` and\n~~~~\ndef foobar(self):\n return self.baz()",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<p>Hamlet said:</p>\n<div class=\"codehilite\"><pre><span></span>def speak(self):\n x = 1\n# Comment to make this code block longer to test Trac #1162\n</pre></div>\n\n\n<p>Then he mentioned <code>y = 4 + x**2</code> and</p>\n<div class=\"codehilite\"><pre><span></span>def foobar(self):\n return self.baz()\n</pre></div>",
tests: Change test_content to text_content in markdown_test_cases. docs: Fix error in markdown documentation.
2017-10-31 10:30:24 +01:00
"text_content": "Hamlet said:\ndef speak(self):\n x = 1\n# Comment to make this code block longer to test Trac #1162\n\n\n\nThen he mentioned y = 4 + x**2 and\ndef foobar(self):\n return self.baz()\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "fenced_quote",
"input": "Hamlet said:\n~~~ quote\nTo be or **not** to be.\n\nThat is the question\n~~~",
"expected_output": "<p>Hamlet said:</p>\n<blockquote>\n<p>To be or <strong>not</strong> to be.</p>\n<p>That is the question</p>\n</blockquote>",
push_notifications: Format blockquotes properly in text_output. New output is of the format: Hamlet said: > Polonius said: > > This is the. > > Second layer of nesting. > First layer of nesting. Fixes #9251.
2018-05-02 07:01:29 +02:00
"text_content": "Hamlet said:\n> To be or not to be.\n> That is the question\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "fenced_nested_quote",
"input": "Hamlet said:\n~~~ quote\nPolonius said:\n> This above all: to thine ownself be true,\nAnd it must follow, as the night the day,\nThou canst not then be false to any man.\n\nWhat good advice!\n~~~",
"expected_output": "<p>Hamlet said:</p>\n<blockquote>\n<p>Polonius said:</p>\n<blockquote>\n<p>This above all: to thine ownself be true,<br>\nAnd it must follow, as the night the day,<br>\nThou canst not then be false to any man.</p>\n</blockquote>\n<p>What good advice!</p>\n</blockquote>",
push_notifications: Format blockquotes properly in text_output. New output is of the format: Hamlet said: > Polonius said: > > This is the. > > Second layer of nesting. > First layer of nesting. Fixes #9251.
2018-05-02 07:01:29 +02:00
"text_content": "Hamlet said:\n> Polonius said:\n> > This above all: to thine ownself be true,\n> > And it must follow, as the night the day,\n> > Thou canst not then be false to any man.\n> What good advice!\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "complexly_nested_quote",
Use our own fenced code preprocessor, fixing output mismatches (imported from commit 3d4abb1043349e30adf265342ee7c946a99b3ce2)
2014-01-27 23:21:48 +01:00
"input": "I heard about this second hand...\n~~~ quote\n\nHe said:\n~~~ quote\nThe customer is complaining.\n\nThey looked at this code:\n``` \ndef hello(): print 'hello\n```\nThey would prefer:\n~~~\ndef hello()\n puts 'hello'\nend\n~~~\n\nPlease advise.\n~~~\n\nShe said:\n~~~ quote\nJust send them this:\n```\necho \"hello\n\"\n```\n~~~",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<p>I heard about this second hand...</p>\n<blockquote>\n<p>He said:</p>\n<blockquote>\n<p>The customer is complaining.</p>\n<p>They looked at this code:</p>\n<div class=\"codehilite\"><pre><span></span>def hello(): print &#39;hello\n</pre></div>\n\n\n<p>They would prefer:</p>\n</blockquote>\n<p>def hello()<br>\n puts 'hello'<br>\nend</p>\n</blockquote>\n<p>Please advise.</p>\n<div class=\"codehilite\"><pre><span></span>She said:\n~~~ quote\nJust send them this:\n```\necho &quot;hello\n&quot;\n```\n</pre></div>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p>I heard about this second hand...</p>\n<blockquote>\n<p>He said:</p>\n<blockquote>\n<p>The customer is complaining.</p>\n<p>They looked at this code:</p>\n<div class=\"codehilite\"><pre><span></span>def hello(): print &#39;hello\n</pre></div>\n\n\n<p>They would prefer:</p>\n</blockquote>\n<p>def hello()<br>\n puts &#39;hello&#39;<br>\nend</p>\n</blockquote>\n<p>Please advise.</p>\n<div class=\"codehilite\"><pre><span></span>\nShe said:\n~~~ quote\nJust send them this:\n```\necho &quot;hello\n&quot;\n```\n</pre></div>",
push_notifications: Format blockquotes properly in text_output. New output is of the format: Hamlet said: > Polonius said: > > This is the. > > Second layer of nesting. > First layer of nesting. Fixes #9251.
2018-05-02 07:01:29 +02:00
"text_content": "I heard about this second hand...\n> He said:\n> > The customer is complaining.\n> > They looked at this code:\n> > def hello(): print 'hello\n> > They would prefer:\n> def hello()\n> puts 'hello'\n> end\n\nPlease advise.\nShe said:\n~~~ quote\nJust send them this:\n```\necho \"hello\n\"\n```\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
bugdown: Fix handling of nested fenced math blocks. Change any fence delimiters (backticks and tildes) to be interpreted literally inside of math fenced_code blocks. Fixes #5190.
2017-11-21 07:21:26 +01:00
{
"name": "fenced_quotes_inside_mathblock",
"input": "```math\n````js\nvar x;\n````\n```",
bugdown: Update KaTeX to version 0.8.3 from 0.7.1. Fixes #7480.
2017-11-23 05:52:13 +01:00
"expected_output": "<p><span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi>j</mi><mi>s</mi><mi>v</mi><mi>a</mi><mi>r</mi><mi>x</mi><mo separator=\"true\">;</mo><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi></mrow><annotation encoding=\"application/x-tex\">````js\nvar x;\n````</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.69444em;\"></span><span class=\"strut bottom\" style=\"height:0.8888799999999999em;vertical-align:-0.19444em;\"></span><span class=\"base\"><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathit\" style=\"margin-right:0.05724em;\">j</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">v</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">x</span><span class=\"mpunct\">;</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span></span></span></span></span></p>",
"marked_expected_output": "<span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi>j</mi><mi>s</mi><mi>v</mi><mi>a</mi><mi>r</mi><mi>x</mi><mo separator=\"true\">;</mo><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi><mi mathvariant=\"normal\">‘</mi></mrow><annotation encoding=\"application/x-tex\">````js\nvar x;\n````</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.69444em;\"></span><span class=\"strut bottom\" style=\"height:0.8888799999999999em;vertical-align:-0.19444em;\"></span><span class=\"base\"><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathit\" style=\"margin-right:0.05724em;\">j</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">v</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">x</span><span class=\"mpunct\">;</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span><span class=\"mord mathrm\">‘</span></span></span></span></span>"
bugdown: Fix handling of nested fenced math blocks. Change any fence delimiters (backticks and tildes) to be interpreted literally inside of math fenced_code blocks. Fixes #5190.
2017-11-21 07:21:26 +01:00
},
bugdown: Properly parse empty blockquotes. The character ">" now only starts a blockquote if the resulting blockquote would be non-empty. Thus, by itself, ">" is now interpreted literally by bugdown, fixing #687. The message with contents consisting of ">>>" is now parsed as a doubly (not triply) nested blockquote with contents ">". Properly formed blockquotes have identical behavior as before, but now bugdown can no longer produce empty blockquotes as output. Fixes #2886, #687.
2017-11-17 11:02:44 +01:00
{
"name": "empty_single_blockquote",
"input": ">",
"expected_output": "<p>&gt;</p>"
},
{
"name": "empty_multiple_blockquote",
"input": ">>>>>",
"expected_output": "<blockquote>\n<blockquote>\n<blockquote>\n<blockquote>\n<p>&gt;</p>\n</blockquote>\n</blockquote>\n</blockquote>\n</blockquote>"
},
{
"name": "non_empty_blockquote",
"input": ">\n>\ntext",
"expected_output": "<blockquote>\n<p>text</p>\n</blockquote>"
},
markdown.js: Move markdown.js test to bugdown-data.json.
2017-07-18 20:24:18 +02:00
{
"name": "fenced_quote_with_hashtag",
"input": "```quote\n# line 1\n# line 2\n```",
"expected_output": "<blockquote>\n<p># line 1<br>\n# line 2</p>\n</blockquote>",
push_notifications: Format blockquotes properly in text_output. New output is of the format: Hamlet said: > Polonius said: > > This is the. > > Second layer of nesting. > First layer of nesting. Fixes #9251.
2018-05-02 07:01:29 +02:00
"text_content": "> # line 1\n> # line 2\n"
markdown.js: Move markdown.js test to bugdown-data.json.
2017-07-18 20:24:18 +02:00
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "dangerous_block",
"input": "xxxxxx xxxxx xxxxxxxx xxxx. x xxxx xxxxxxxxxx:\n\n```\"xxxx xxxx\\xxxxx\\xxxxxx\"```\n\nxxx xxxx xxxxx:```xx.xxxxxxx(x'^xxxx$', xx.xxxxxxxxx)```\n\nxxxxxxx'x xxxx xxxxxxxxxx ```'xxxx'```, xxxxx xxxxxxxxx xxxxx ^ xxx $ xxxxxx xxxxx xxxxxxxxxxxx xxx xxxx xx x xxxx xx xxxx xx xxx xxxxx xxxxxx?",
"expected_output": "<p>xxxxxx xxxxx xxxxxxxx xxxx. x xxxx xxxxxxxxxx:</p>\n<p><code>\"xxxx xxxx\\xxxxx\\xxxxxx\"</code></p>\n<p>xxx xxxx xxxxx:<code>xx.xxxxxxx(x'^xxxx$', xx.xxxxxxxxx)</code></p>\n<p>xxxxxxx'x xxxx xxxxxxxxxx <code>'xxxx'</code>, xxxxx xxxxxxxxx xxxxx ^ xxx $ xxxxxx xxxxx xxxxxxxxxxxx xxx xxxx xx x xxxx xx xxxx xx xxx xxxxx xxxxxx?</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "xxxxxx xxxxx xxxxxxxx xxxx. x xxxx xxxxxxxxxx:\n\"xxxx xxxx\\xxxxx\\xxxxxx\"\nxxx xxxx xxxxx:xx.xxxxxxx(x'^xxxx$', xx.xxxxxxxxx)\nxxxxxxx'x xxxx xxxxxxxxxx 'xxxx', xxxxx xxxxxxxxx xxxxx ^ xxx $ xxxxxx xxxxx xxxxxxxxxxxx xxx xxxx xx x xxxx xx xxxx xx xxx xxxxx xxxxxx?"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "dangerous_block",
"input": "``` one ```\n\n``` two ```\n\n~~~~\nx = 1",
bugdown: Remove whitespace strip from inline code. Fixes #4507
2017-11-22 02:27:19 +01:00
"expected_output": "<p><code> one </code></p>\n<p><code> two </code></p>\n<div class=\"codehilite\"><pre><span></span>x = 1\n</pre></div>",
"text_content": " one \n two \nx = 1\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
{
"name": "four_space_code_block",
"input": " def foo(): pass",
"expected_output": "<div class=\"codehilite\"><pre><span></span>def foo(): pass\n</pre></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"marked_expected_output": "<div class=\"codehilite\"><pre>def foo(): pass\n</pre></div>",
"text_content": "def foo(): pass\n"
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
},
{
"name": "two_space_not_code_block",
"input": " notcode",
"expected_output": "<p>notcode</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"marked_expected_output": "<p> notcode</p>",
"text_content": "notcode"
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "ulist_standard",
"input": "Some text with a list:\n\n* One item\n* Two items\n* Three items",
"expected_output": "<p>Some text with a list:</p>\n<ul>\n<li>One item</li>\n<li>Two items</li>\n<li>Three items</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Some text with a list:\n\nOne item\nTwo items\nThree items\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "ulist_hanging",
"input": "Some text with a hanging list:\n* One item\n* Two items\n* Three items",
"expected_output": "<p>Some text with a hanging list:</p>\n<ul>\n<li>One item</li>\n<li>Two items</li>\n<li>Three items</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Some text with a hanging list:\n\nOne item\nTwo items\nThree items\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "ulist_hanging_mixed",
"input": "Plain list\n\n* Alpha\n\n* Beta\n\nThen hang it off:\n* Ypsilon\n* Zeta",
"expected_output": "<p>Plain list</p>\n<ul>\n<li>\n<p>Alpha</p>\n</li>\n<li>\n<p>Beta</p>\n</li>\n</ul>\n<p>Then hang it off:</p>\n<ul>\n<li>Ypsilon</li>\n<li>Zeta</li>\n</ul>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p>Plain list</p>\n<ul>\n<li><p>Alpha</p>\n</li>\n<li><p>Beta</p>\n</li>\n</ul>\n<p>Then hang it off:</p>\n<ul>\n<li>Ypsilon</li>\n<li>Zeta</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Plain list\n\n\nAlpha\n\n\nBeta\n\n\nThen hang it off:\n\nYpsilon\nZeta\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "ulist_hanging_multi",
"input": "Plain list\n* Alpha\n* Beta\n\nAnd Again:\n* A\n* B\n* C\n\nOnce more for feeling:\n* Q\n* E\n* D",
"expected_output": "<p>Plain list</p>\n<ul>\n<li>Alpha</li>\n<li>Beta</li>\n</ul>\n<p>And Again:</p>\n<ul>\n<li>A</li>\n<li>B</li>\n<li>C</li>\n</ul>\n<p>Once more for feeling:</p>\n<ul>\n<li>Q</li>\n<li>E</li>\n<li>D</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Plain list\n\nAlpha\nBeta\n\nAnd Again:\n\nA\nB\nC\n\nOnce more for feeling:\n\nQ\nE\nD\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
{
"name": "ulist_nested_ulist_two_space_indent",
"input": "Nested list\n* I am outer list\n * I am inner nested list first item\n * I am inner nested list second item",
"expected_output": "<p>Nested list</p>\n<ul>\n<li>I am outer list<ul>\n<li>I am inner nested list first item</li>\n<li>I am inner nested list second item</li>\n</ul>\n</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Nested list\n\nI am outer list\nI am inner nested list first item\nI am inner nested list second item\n\n\n"
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
},
{
"name": "ulist_list_two_space_indent",
"input": "* I am outer list\n I am something inside",
"expected_output": "<ul>\n<li>I am outer list<br>\n I am something inside</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"marked_expected_output": "<ul>\n<li>I am outer list<br>\nI am something inside</li>\n</ul>",
"text_content": "\nI am outer list\n I am something inside\n"
markdown: Render backend second level markdown. By default, Python markdown tab length for indents is 4 spaces, which require using 4 spaces or a tab to create nested elements. This modifies that setting to specify 2-space indentation for nesting elements only. Modified significantly by tabbott to limit the change to just list indentation. Fixes #4252.
2017-03-26 21:14:05 +02:00
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "ulist_codeblock",
"input": "~~~\nint x = 3\n* 4;\n~~~",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<div class=\"codehilite\"><pre><span></span>int x = 3\n* 4;\n</pre></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "int x = 3\n* 4;\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "malformed_fence",
"input": "~~~~~~~~xxxxxxxxx: xxxxxxxxxxxx xxxxx x xxxxxxxx~~~~~~",
"expected_output": "<p>~~~~~~~~xxxxxxxxx: xxxxxxxxxxxx xxxxx x xxxxxxxx~~~~~~</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "~~~~~~~~xxxxxxxxx: xxxxxxxxxxxx xxxxx x xxxxxxxx~~~~~~"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
bugdown: Add support for strikethrough in markdown processor. [Tweaked to move tests to bugdown_data.json, add additional tests, and add frontend processor support by tabbott]
2016-11-08 07:26:38 +01:00
{
"name": "strikthrough_basic",
"input": "I like ~~software~~ hardware",
"expected_output": "<p>I like <del>software</del> hardware</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "I like software hardware"
bugdown: Add support for strikethrough in markdown processor. [Tweaked to move tests to bugdown_data.json, add additional tests, and add frontend processor support by tabbott]
2016-11-08 07:26:38 +01:00
},
{
"name": "strikthrough_multiword",
"input": "I ~~like software~~ love hardware",
"expected_output": "<p>I <del>like software</del> love hardware</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "I like software love hardware"
bugdown: Add support for strikethrough in markdown processor. [Tweaked to move tests to bugdown_data.json, add additional tests, and add frontend processor support by tabbott]
2016-11-08 07:26:38 +01:00
},
{
"name": "strikthrough_multiword",
"input": "I ~~ like software ~~ love hardware",
"expected_output": "<p>I <del> like software </del> love hardware</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "I like software love hardware"
bugdown: Add support for strikethrough in markdown processor. [Tweaked to move tests to bugdown_data.json, add additional tests, and add frontend processor support by tabbott]
2016-11-08 07:26:38 +01:00
},
markdown: Update regex for strikethrough. This uses the correct regex for strikethrough. Also, added a test to make sure that strikethrough works when it contains link with whitespace. Fixes #7596.
2017-12-22 12:51:08 +01:00
{
"name": "strikthrough_link",
"input": "~~test http://xx.xx link~~",
"expected_output": "<p><del>test <a href=\"http://xx.xx\" target=\"_blank\" title=\"http://xx.xx\">http://xx.xx</a> link</del></p>",
"text_content": "test http://xx.xx link"
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "underscore_disabled",
"input": "_foo_",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>_foo_</p>"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
bugdown: Re-enable support for italics in bugdown. Fixes: #1103.
2016-11-03 07:56:28 +01:00
"name": "emphasis_text",
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
"input": "*foo*",
bugdown: Re-enable support for italics in bugdown. Fixes: #1103.
2016-11-03 07:56:28 +01:00
"expected_output": "<p><em>foo</em></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "foo"
bugdown: Re-enable support for italics in bugdown. Fixes: #1103.
2016-11-03 07:56:28 +01:00
},
{
"name": "emphasis_code",
"input": "const char *x = (char *)y",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>const char *x = (char *)y</p>"
bugdown: Re-enable support for italics in bugdown. Fixes: #1103.
2016-11-03 07:56:28 +01:00
},
{
"name": "emphasis_with_space",
"input": "A *foo bar* is a *baz quux*",
"expected_output": "<p>A <em>foo bar</em> is a <em>baz quux</em></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "A foo bar is a baz quux"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
CVE-2018-9986: Fix XSS issues with frontend markdown processor. This fixes a set of XSS issues with Zulip's frontend markdown processor, which is used in a limited set of contexts, such as local echo of messages and the drafts feature. The implementation of several syntax elements, including the <em> syntax, user and stream mentions, and some others failed to properly escape the content inside the syntax. Fix this, and add tests for each corrected code path. Thanks to w2w for reporting this issue.
2018-03-29 00:25:58 +02:00
{
"name": "emphasis_with_html",
"input": "*<h1>Hello World</h1>*",
"expected_output": "<p><em>&lt;h1&gt;Hello World&lt;/h1&gt;</em></p>"
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "underscore_strong_disabled",
"input": "__foo__",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>__foo__</p>"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "star_strong",
"input": "**foo**",
"expected_output": "<p><strong>foo</strong></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "foo"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
markdown: Apply both bold and italic for words like ***text***. Adds rule 'strong_em' to markdown parser to recognize ***{TEXT}*** Fixes #8155.
2018-02-17 01:59:22 +01:00
{
"name": "star_strong_em",
"input": "***foo***",
"expected_output": "<p><strong><em>foo</em></strong></p>",
"text_content": "foo"
},
CVE-2018-9986: Fix XSS issues with frontend markdown processor. This fixes a set of XSS issues with Zulip's frontend markdown processor, which is used in a limited set of contexts, such as local echo of messages and the drafts feature. The implementation of several syntax elements, including the <em> syntax, user and stream mentions, and some others failed to properly escape the content inside the syntax. Fix this, and add tests for each corrected code path. Thanks to w2w for reporting this issue.
2018-03-29 00:25:58 +02:00
{
"name": "strong_with_html",
"input": "**<h1>Hello World</h1>**",
"expected_output": "<p><strong>&lt;h1&gt;Hello World&lt;/h1&gt;</strong></p>"
},
markdown.js: Remove paragraph break from numbered lists. Fixes #5902.
2017-07-28 06:28:45 +02:00
{
"name": "numbered_list",
"input": "1. A\n 2. B",
"expected_output": "<p>1. A<br>\n 2. B</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "1. A\n 2. B"
markdown.js: Remove paragraph break from numbered lists. Fixes #5902.
2017-07-28 06:28:45 +02:00
},
markdown: Add automatic numbering of ordered lists. Adds a markdown preprocessor that finds ordered lists where all items use the same number and change them to be in normal increasing order, starting with that number. Fixes #5159.
2017-12-03 15:24:21 +01:00
{
"name": "auto_renumbered_list",
"input": "1. A\n1. B\n 1. C\n1. D",
"expected_output": "<p>1. A<br>\n2. B<br>\n 3. C<br>\n4. D</p>",
"text_content": "1. A\n2. B\n 3. C\n4. D"
},
{
"name": "auto_renumbered_list_from",
"input": "3. A\n3. B\n3. C\n3. D",
"expected_output": "<p>3. A<br>\n4. B<br>\n5. C<br>\n6. D</p>",
"text_content": "3. A\n4. B\n5. C\n6. D"
},
{
"name": "not_auto_renumbered_list",
"input": "1. A\n3. B\n 2. C\n1. D",
"expected_output": "<p>1. A<br>\n3. B<br>\n 2. C<br>\n1. D</p>",
"text_content": "1. A\n3. B\n 2. C\n1. D"
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "linkify_interference",
"input": "link: xx, x xxxxx xx xxxx xx\n\n[xxxxx #xx](http://xxxxxxxxx:xxxx/xxx/xxxxxx%xxxxxx/xx/):**xxxxxxx**\n\nxxxxxxx xxxxx xxxx xxxxx:\n`xxxxxx`: xxxxxxx\n`xxxxxx`: xxxxx\n`xxxxxx`: xxxxx xxxxx",
"expected_output": "<p>link: xx, x xxxxx xx xxxx xx</p>\n<p><a href=\"http://xxxxxxxxx:xxxx/xxx/xxxxxx%xxxxxx/xx/\" target=\"_blank\" title=\"http://xxxxxxxxx:xxxx/xxx/xxxxxx%xxxxxx/xx/\">xxxxx #xx</a>:<strong>xxxxxxx</strong></p>\n<p>xxxxxxx xxxxx xxxx xxxxx:<br>\n<code>xxxxxx</code>: xxxxxxx<br>\n<code>xxxxxx</code>: xxxxx<br>\n<code>xxxxxx</code>: xxxxx xxxxx</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "link: xx, x xxxxx xx xxxx xx\nxxxxx #xx:xxxxxxx\nxxxxxxx xxxxx xxxx xxxxx:\nxxxxxx: xxxxxxx\nxxxxxx: xxxxx\nxxxxxx: xxxxx xxxxx"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "inline_image",
"input": "Google logo today: https://www.google.com/images/srpr/logo4w.png\nKinda boring",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<p>Google logo today: <a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">https://www.google.com/images/srpr/logo4w.png</a><br>\nKinda boring</p>\n<div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"backend_only_rendering": true,
"text_content": "Google logo today: https:\/\/www.google.com\/images\/srpr\/logo4w.png\nKinda boring\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
{
"name": "blockquote_inline_image",
"input": ">Google logo today:\n>https://www.google.com/images/srpr/logo4w.png\n>Kinda boring",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<blockquote>\n<p>Google logo today:<br>\n<a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">https://www.google.com/images/srpr/logo4w.png</a><br>\nKinda boring</p>\n<div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div></blockquote>",
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
"backend_only_rendering": true,
push_notifications: Format blockquotes properly in text_output. New output is of the format: Hamlet said: > Polonius said: > > This is the. > > Second layer of nesting. > First layer of nesting. Fixes #9251.
2018-05-02 07:01:29 +02:00
"text_content": "> Google logo today:\n> https:\/\/www.google.com\/images\/srpr\/logo4w.png\n> Kinda boring\n"
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "two_inline_images",
"input": "Google logo today: https://www.google.com/images/srpr/logo4w.png\nKinda boringGoogle logo today: https://www.google.com/images/srpr/logo4w.png\nKinda boring",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<p>Google logo today: <a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">https://www.google.com/images/srpr/logo4w.png</a><br>\nKinda boringGoogle logo today: <a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">https://www.google.com/images/srpr/logo4w.png</a><br>\nKinda boring</p>\n<div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div><div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"backend_only_rendering": true,
"text_content": "Google logo today: https:\/\/www.google.com\/images\/srpr\/logo4w.png\nKinda boringGoogle logo today: https:\/\/www.google.com\/images\/srpr\/logo4w.png\nKinda boring\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
{
"name": "bulleted_list_inlining",
"input": "* Google?\n* Google. https://www.google.com/images/srpr/logo4w.png\n* Google!",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<ul>\n<li>Google?</li>\n<li>Google. <a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">https://www.google.com/images/srpr/logo4w.png</a><div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div></li>\n<li>Google!</li>\n</ul>",
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
"backend_only_rendering": true,
"text_content": "\nGoogle?\nGoogle. https://www.google.com/images/srpr/logo4w.png\nGoogle!\n"
},
markdown: Hide URL if message is only an image. Hides URL if the message content == image url so that sending gifs or images feels less cluttered. Uses the url_to_a() function to generate the expected url string for matching. Fixes #7324.
2017-11-27 10:03:18 +01:00
{
"name": "only_inline_image",
"input": "https://www.google.com/images/srpr/logo4w.png",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div>",
markdown: Hide URL if message is only an image. Hides URL if the message content == image url so that sending gifs or images feels less cluttered. Uses the url_to_a() function to generate the expected url string for matching. Fixes #7324.
2017-11-27 10:03:18 +01:00
"backend_only_rendering": true
},
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
{
"name": "only_named_inline_image",
"input": "[Google Link](https://www.google.com/images/srpr/logo4w.png)",
thumbnails: Rename size value 'original' to 'full'.
2018-07-30 21:26:01 +02:00
"expected_output": "<p><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"https://www.google.com/images/srpr/logo4w.png\">Google Link</a></p>\n<div class=\"message_inline_image\"><a href=\"https://www.google.com/images/srpr/logo4w.png\" target=\"_blank\" title=\"Google Link\"><img data-src-fullsize=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=full\" src=\"/thumbnail?url=https%3A%2F%2Fwww.google.com%2Fimages%2Fsrpr%2Flogo4w.png&amp;size=thumbnail\"></a></div>",
bugdown: Improve image inlining logic. Fix #7537
2017-12-25 21:35:23 +01:00
"backend_only_rendering": true,
"text_content": "Google Link\n"
},
markdown: Hide URL if message is only an image. Hides URL if the message content == image url so that sending gifs or images feels less cluttered. Uses the url_to_a() function to generate the expected url string for matching. Fixes #7324.
2017-11-27 10:03:18 +01:00
{
"name": "only_non_image_link",
"input": "https://github.com",
"expected_output": "<p><a href=\"https://github.com\" target=\"_blank\" title=\"https://github.com\">https://github.com</a></p>"
},
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
{
"name": "nl2br",
"input": "test\nbar",
"expected_output": "<p>test<br>\nbar</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "test\nbar"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "nl2br_trailing_space",
"input": "test ",
"expected_output": "<p>test </p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "test "
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "tables",
"input": "This is a table:\n\nFirst Header | Second Header\n------------- | -------------\nContent Cell | Content Cell\nContent Cell | Content Cell\n",
"expected_output": "<p>This is a table:</p>\n<table>\n<thead>\n<tr>\n<th>First Header</th>\n<th>Second Header</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Content Cell</td>\n<td>Content Cell</td>\n</tr>\n<tr>\n<td>Content Cell</td>\n<td>Content Cell</td>\n</tr>\n</tbody>\n</table>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "This is a table:\n\n\n\nFirst Header\nSecond Header\n\n\n\n\nContent Cell\nContent Cell\n\n\nContent Cell\nContent Cell\n\n\n"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
},
{
"name": "multiline_strong",
"input": "You can check out **any time you'd like\nBut you can never leave**",
"expected_output": "<p>You can check out **any time you'd like<br>\nBut you can never leave**</p>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p>You can check out <strong>any time you&#39;d like<br>\nBut you can never leave</strong></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "You can check out **any time you'd like\nBut you can never leave**"
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
},
{
"name": "many_emoji",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"input": "test :smile: again :poop:\n:) foo:)bar x::y::z :wasted waste: :fakeemojithisshouldnotrender:",
"expected_output": "<p>test <span class=\"emoji emoji-263a\" title=\"smile\">:smile:</span> again <span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span><br>\n:) foo:)bar x::y::z :wasted waste: :fakeemojithisshouldnotrender:</p>",
"text_content": "test \u263A again \ud83d\udca9\n:) foo:)bar x::y::z :wasted waste: :fakeemojithisshouldnotrender:"
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
},
emoji: Add translate_emoticons flag in bugdown testcases. Also switches the default behaviour of the code to not translate the emoticons. Earlier, the code was testing-aware, and used to translate when there was no user profile data available(assuming that as a testing environment).
2018-03-25 23:23:22 +02:00
{
"name": "translate_emoticons_not_enabled",
"input": ":)",
"expected_output": "<p>:)</p>",
"text_content": ":)",
"translate_emoticons": false
},
{
"name": "translate_emoticons_enabled",
"input": ":)",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"expected_output": "<p><span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span></p>",
"text_content": "\ud83d\ude42",
emoji: Add translate_emoticons flag in bugdown testcases. Also switches the default behaviour of the code to not translate the emoticons. Earlier, the code was testing-aware, and used to translate when there was no user profile data available(assuming that as a testing environment).
2018-03-25 23:23:22 +02:00
"translate_emoticons": true
},
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
{
"name": "translate_emoticons",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"input": ":) foo :( bar <3 with space : ) real emoji :slight_smile:",
"expected_output": "<p><span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span> foo <span class=\"emoji emoji-1f641\" title=\"frown\">:frown:</span> bar <span class=\"emoji emoji-2764\" title=\"heart\">:heart:</span> with space : ) real emoji <span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span></p>",
"text_content": "\ud83d\ude42 foo \ud83d\ude41 bar \u2764 with space : ) real emoji \ud83d\ude42",
emoji: Add translate_emoticons flag in bugdown testcases. Also switches the default behaviour of the code to not translate the emoticons. Earlier, the code was testing-aware, and used to translate when there was no user profile data available(assuming that as a testing environment).
2018-03-25 23:23:22 +02:00
"translate_emoticons": true
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
},
{
"name": "translate_emoticons_whitepsace",
"input": "a:) ;)b",
"expected_output": "<p>a:) ;)b</p>",
emoji: Add translate_emoticons flag in bugdown testcases. Also switches the default behaviour of the code to not translate the emoticons. Earlier, the code was testing-aware, and used to translate when there was no user profile data available(assuming that as a testing environment).
2018-03-25 23:23:22 +02:00
"text_content": "a:) ;)b",
"translate_emoticons": true
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
},
emoji: Fix a bug where emoticon translation is not done after a newline. This bug is caused by the conversion of newlines to `<br>` statements, since `>` is not allowed as a character around an emoticon during translation. Also, add a new test case for preventing this bug from occurring in the future. Fix #9763.
2018-06-20 17:09:18 +02:00
{
"name": "translate_emoticons_newline",
"input": ":) test\n:) test",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"expected_output": "<p><span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span> test<br>\n<span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span> test</p>",
"text_content": "\ud83d\ude42 test\n\ud83d\ude42 test",
emoji: Fix a bug where emoticon translation is not done after a newline. This bug is caused by the conversion of newlines to `<br>` statements, since `>` is not allowed as a character around an emoticon during translation. Also, add a new test case for preventing this bug from occurring in the future. Fix #9763.
2018-06-20 17:09:18 +02:00
"translate_emoticons": true
},
emoji: Add support for translating emoticons. Add `translate_emoticons` to `prop_types` and `expected_keys`. Furthermore, create a emoji-translating Markdown inline pattern. Also use a JavaScript version of `translate_emoticons` and then use this function during Markdown previews and as a preprocessor. This is only needed for previews, because usually emoticon translation happens on the backend after sending. Add tests for emoticon translation, a settings UI, and a /help/ page as well. Tweaked by tabbott to fix various test failurse as well as how this handles whitespace, requiring emoticons to not have adjacent characters. Fixes #1768.
2018-01-15 19:36:32 +01:00
{
"name": "translate_emoticons_in_code",
"input": "`:)`",
"expected_output": "<p><code>:)</code></p>",
emoji: Add translate_emoticons flag in bugdown testcases. Also switches the default behaviour of the code to not translate the emoticons. Earlier, the code was testing-aware, and used to translate when there was no user profile data available(assuming that as a testing environment).
2018-03-25 23:23:22 +02:00
"text_content": ":)",
"translate_emoticons": true
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
},
markdown: Update bugdown emoticon translation logic to match frontend. This PR solves some of the parity issues in the emoticon translation logic. I was unable to find a way of matching only one of the lookaround groups, so we still have some inconsistency (see testcase). The approach of having another check while converting just for this seemed like an inefficient way, so I've left that last change as it is.
2018-03-30 00:34:25 +02:00
{
"name": "translate_emoticons_at_sentence_end",
"input": "Translate this :).",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"expected_output": "<p>Translate this <span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span>.</p>",
"text_content": "Translate this \ud83d\ude42.",
markdown: Update bugdown emoticon translation logic to match frontend. This PR solves some of the parity issues in the emoticon translation logic. I was unable to find a way of matching only one of the lookaround groups, so we still have some inconsistency (see testcase). The approach of having another check while converting just for this seemed like an inefficient way, so I've left that last change as it is.
2018-03-30 00:34:25 +02:00
"translate_emoticons": true
},
{
"name": "translate_emoticons_between_symbols",
"input": "Translate this !:)?",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"expected_output": "<p>Translate this !<span class=\"emoji emoji-1f642\" title=\"slight smile\">:slight_smile:</span>?</p>",
markdown: Update bugdown emoticon translation logic to match frontend. This PR solves some of the parity issues in the emoticon translation logic. I was unable to find a way of matching only one of the lookaround groups, so we still have some inconsistency (see testcase). The approach of having another check while converting just for this seemed like an inefficient way, so I've left that last change as it is.
2018-03-30 00:34:25 +02:00
"marked_expected_output": "<p>Translate this !:)?</p>",
emoji: Change emoticon mapping for `:)`, `(:` and `:(`. See discussion on CZO: https://chat.zulip.org/#narrow/stream/101-design/subject/emoji.20picker/near/617811
2018-07-26 19:35:28 +02:00
"text_content": "Translate this !\ud83d\ude42?",
markdown: Update bugdown emoticon translation logic to match frontend. This PR solves some of the parity issues in the emoticon translation logic. I was unable to find a way of matching only one of the lookaround groups, so we still have some inconsistency (see testcase). The approach of having another check while converting just for this seemed like an inefficient way, so I've left that last change as it is.
2018-03-30 00:34:25 +02:00
"translate_emoticons": true
},
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
{
"name": "random_emoji_1",
emoji: Remove duplicates from autocomplete and emoji picker. Previously, if you searched for ':offi..' you would see both :office: and :office_building: as possible completions, both of which are shortcodes for the same unicode codepoint (and hence which have the same image). Also, we sort the emoji in our emoji pickers alphabetically by shortcode, and so the images for :office: and :office_building: show up next to each other, which looks like a bug. This removes :office_building: as a shortcode, along with several hundred other duplicates. It leaves some duplicates in that won't give autocomplete or alphabetical ordering a problem, like (:car:, :automobile:).
2017-01-26 08:35:23 +01:00
"input": ":airplane:",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p><span class=\"emoji emoji-2708\" title=\"airplane\">:airplane:</span></p>"
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
},
bugdown: Add a Zulip emoji test.
2017-02-27 03:27:20 +01:00
{
"name": "zulip_emoji",
"input": ":zulip:",
emoji: Change emoji image titles to use spaces instead of underscores. Previously, the emoji images title display `:baby_bottle:`. This commit changes the title to display `baby bottle`.
2017-06-09 10:30:24 +02:00
"expected_output": "<p><img alt=\":zulip:\" class=\"emoji\" src=\"/static/generated/emoji/images/emoji/unicode/zulip.png\" title=\"zulip\"></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": ":zulip:"
bugdown: Add a Zulip emoji test.
2017-02-27 03:27:20 +01:00
},
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
{
"name": "random_emoji_2",
"input": ":poop:",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p><span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span></p>"
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
},
Support backend emoji rendering without whitespace.
2016-11-08 12:20:56 +01:00
{
"name": "emojis_without_space",
"input": ":cat:hello:dog::rabbit:",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output": "<p><span class=\"emoji emoji-1f408\" title=\"cat\">:cat:</span>hello<span class=\"emoji emoji-1f415\" title=\"dog\">:dog:</span><span class=\"emoji emoji-1f407\" title=\"rabbit\">:rabbit:</span></p>",
"text_content": "\ud83d\udc08hello\ud83d\udc15\ud83d\udc07"
Support backend emoji rendering without whitespace.
2016-11-08 12:20:56 +01:00
},
{
"name": "emojis_newline",
"input": ":cat:\n:dog:",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output": "<p><span class=\"emoji emoji-1f408\" title=\"cat\">:cat:</span><br>\n<span class=\"emoji emoji-1f415\" title=\"dog\">:dog:</span></p>",
"text_content": "\ud83d\udc08\n\ud83d\udc15"
Support backend emoji rendering without whitespace.
2016-11-08 12:20:56 +01:00
},
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
{
"name": "not_emoji",
"input": ":not_an_emoji:",
"expected_output": "<p>:not_an_emoji:</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": ":not_an_emoji:"
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
},
Add unicode emoji to frontend markdown parser. Fixes 2nd half of #1011.
2016-06-24 22:39:44 +02:00
{
"name": "unicode_emoji",
"input": "\ud83d\udca9",
emoji: Migrate bugdown emoji to use sprite sheets. This commit switches to use sprite sheets for rendering emojis in all the remaining places, i.e., message bodies and composebox typeahead. This commit also includes some changes to notifications.py file so that the spans used for rendering emojis can be converted to corresponding image tags so that we don't break the emoji rendering in missed message emails since we can't use sprite sheets there. As part of switching the bugdown system to use sprite sheets, we need to switch the name_to_codepoint mappings to match the new sprite sheets. This has the side effect of fixing a bunch of emoji like numbers and flag emoji in the emoji pickers. Fixes: #3895. Fixes: #3972.
2017-09-27 19:39:42 +02:00
"expected_output":"<p><span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "\ud83d\udca9"
Add unicode emoji to frontend markdown parser. Fixes 2nd half of #1011.
2016-06-24 22:39:44 +02:00
},
{
"name": "two_unicode_emoji",
"input": "\ud83d\udca9\ud83d\udca9",
emoji: Migrate bugdown emoji to use sprite sheets. This commit switches to use sprite sheets for rendering emojis in all the remaining places, i.e., message bodies and composebox typeahead. This commit also includes some changes to notifications.py file so that the spans used for rendering emojis can be converted to corresponding image tags so that we don't break the emoji rendering in missed message emails since we can't use sprite sheets there. As part of switching the bugdown system to use sprite sheets, we need to switch the name_to_codepoint mappings to match the new sprite sheets. This has the side effect of fixing a bunch of emoji like numbers and flag emoji in the emoji pickers. Fixes: #3895. Fixes: #3972.
2017-09-27 19:39:42 +02:00
"expected_output":"<p><span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span><span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span><\/p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "\ud83d\udca9\ud83d\udca9"
Add unicode emoji to frontend markdown parser. Fixes 2nd half of #1011.
2016-06-24 22:39:44 +02:00
},
{
"name": "two_unicode_emoji_separated_by_text",
"input": "\ud83d\udca9 word \ud83d\udca9",
emoji: Migrate bugdown emoji to use sprite sheets. This commit switches to use sprite sheets for rendering emojis in all the remaining places, i.e., message bodies and composebox typeahead. This commit also includes some changes to notifications.py file so that the spans used for rendering emojis can be converted to corresponding image tags so that we don't break the emoji rendering in missed message emails since we can't use sprite sheets there. As part of switching the bugdown system to use sprite sheets, we need to switch the name_to_codepoint mappings to match the new sprite sheets. This has the side effect of fixing a bunch of emoji like numbers and flag emoji in the emoji pickers. Fixes: #3895. Fixes: #3972.
2017-09-27 19:39:42 +02:00
"expected_output":"<p><span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span> word <span class=\"emoji emoji-1f4a9\" title=\"poop\">:poop:</span><\/p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "\ud83d\udca9 word \ud83d\udca9"
Add unicode emoji to frontend markdown parser. Fixes 2nd half of #1011.
2016-06-24 22:39:44 +02:00
},
bugdown: Fix the regex used for unicode emoji matching. The regex we were using didn't cover all the unicode blocks to which our emojis belong. This commit fixes the regex to include all the unicode blocks and also updates the corresponding JS regex in marked.js. Fixes: #3460.
2017-05-15 11:24:01 +02:00
{
"name": "miscellaneous_symbols_and_pictographs",
"input": "Merry Christmas!!\ud83c\udf84",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output":"<p>Merry Christmas!!<span class=\"emoji emoji-1f384\" title=\"holiday tree\">:holiday_tree:</span><\/p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Merry Christmas!!\ud83c\udf84"
bugdown: Fix the regex used for unicode emoji matching. The regex we were using didn't cover all the unicode blocks to which our emojis belong. This commit fixes the regex to include all the unicode blocks and also updates the corresponding JS regex in marked.js. Fixes: #3460.
2017-05-15 11:24:01 +02:00
},
Add marked.js support to emojis in miscellaneous and dingbats block. https://en.wikipedia.org/wiki/Emoji#Unicode_blocks
2016-11-12 23:37:47 +01:00
{
"name": "miscellaneous_and_dingbats_emoji",
"input": "\u2693\u2797",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output":"<p><span class=\"emoji emoji-2693\" title=\"anchor\">:anchor:</span><span class=\"emoji emoji-2797\" title=\"division\">:division:</span><\/p>"
Add marked.js support to emojis in miscellaneous and dingbats block. https://en.wikipedia.org/wiki/Emoji#Unicode_blocks
2016-11-12 23:37:47 +01:00
},
bugdown: Fix the regex used for unicode emoji matching. The regex we were using didn't cover all the unicode blocks to which our emojis belong. This commit fixes the regex to include all the unicode blocks and also updates the corresponding JS regex in marked.js. Fixes: #3460.
2017-05-15 11:24:01 +02:00
{
"name": "supplemental_symbols_and_pictographs",
"input": "I am a robot \ud83e\udd16.",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output":"<p>I am a robot <span class=\"emoji emoji-1f916\" title=\"robot\">:robot:</span>.<\/p>"
bugdown: Fix the regex used for unicode emoji matching. The regex we were using didn't cover all the unicode blocks to which our emojis belong. This commit fixes the regex to include all the unicode blocks and also updates the corresponding JS regex in marked.js. Fixes: #3460.
2017-05-15 11:24:01 +02:00
},
{
"name": "miscellaneous_symbols_and_arrows",
"input": "Black upward arrow \u2b06",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output":"<p>Black upward arrow <span class=\"emoji emoji-2b06\" title=\"up\">:up:</span><\/p>"
bugdown: Fix the regex used for unicode emoji matching. The regex we were using didn't cover all the unicode blocks to which our emojis belong. This commit fixes the regex to include all the unicode blocks and also updates the corresponding JS regex in marked.js. Fixes: #3460.
2017-05-15 11:24:01 +02:00
},
Support backend unicode-emoji rendering without whitespace.
2016-11-12 19:10:51 +01:00
{
"name": "unicode_emoji_without_space",
"input": "Extra\ud83d\udc7dTerrestrial",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output":"<p>Extra<span class=\"emoji emoji-1f47d\" title=\"alien\">:alien:</span>Terrestrial<\/p>"
Support backend unicode-emoji rendering without whitespace.
2016-11-12 19:10:51 +01:00
},
{
"name": "unicode_emojis_new_line",
"input": "\ud83d\udc7d\n\ud83d\udc7d",
emoji: Migrate bugdown emoji to use sprite sheets. This commit switches to use sprite sheets for rendering emojis in all the remaining places, i.e., message bodies and composebox typeahead. This commit also includes some changes to notifications.py file so that the spans used for rendering emojis can be converted to corresponding image tags so that we don't break the emoji rendering in missed message emails since we can't use sprite sheets there. As part of switching the bugdown system to use sprite sheets, we need to switch the name_to_codepoint mappings to match the new sprite sheets. This has the side effect of fixing a bunch of emoji like numbers and flag emoji in the emoji pickers. Fixes: #3895. Fixes: #3972.
2017-09-27 19:39:42 +02:00
"expected_output":"<p><span class=\"emoji emoji-1f47d\" title=\"alien\">:alien:</span><br>\n<span class=\"emoji emoji-1f47d\" title=\"alien\">:alien:</span></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "\ud83d\udc7d\n\ud83d\udc7d"
Support backend unicode-emoji rendering without whitespace.
2016-11-12 19:10:51 +01:00
},
Consolidate emoji tests and test on frontend as well (imported from commit 3244a93209b56b655b80633713a3f58ae46d06ff)
2014-01-24 22:52:37 +01:00
{
"name": "emoji_alongside_punctuation",
"input": ":smile:, :smile:; :smile:",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"expected_output": "<p><span class=\"emoji emoji-263a\" title=\"smile\">:smile:</span>, <span class=\"emoji emoji-263a\" title=\"smile\">:smile:</span>; <span class=\"emoji emoji-263a\" title=\"smile\">:smile:</span></p>"
[localecho] Properly escape HTML in code blocks (imported from commit 11f7e4f440cdd3a2ef6debb10c3d5a07f4fd1a1a)
2014-02-03 17:13:40 +01:00
},
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
{
"name": "new_emoji_test",
build_emoji: Migrate to use `emoji_names.py` file. This migrates Zulip to use a dramatically better set of names and aliases for our emoji set, defined in emoji_names.py (which is in turn manually generated from our hand-curated CSV file). This should significantly improve the experience of using Zulip's emoji picker and emoji typeahead for finding what one is looking for.
2017-11-08 19:40:43 +01:00
"input": ":avocado:, :kiwi:, :selfie:, :gear:, :comet:, :gold:",
"expected_output": "<p><span class=\"emoji emoji-1f951\" title=\"avocado\">:avocado:</span>, <span class=\"emoji emoji-1f95d\" title=\"kiwi\">:kiwi:</span>, <span class=\"emoji emoji-1f933\" title=\"selfie\">:selfie:</span>, <span class=\"emoji emoji-2699\" title=\"gear\">:gear:</span>, <span class=\"emoji emoji-2604\" title=\"comet\">:comet:</span>, <span class=\"emoji emoji-1f947\" title=\"gold\">:gold:</span></p>"
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
},
emoji: Add some edge-casey ordering tests for emoji. Add 3 new Markdown emoji tests for newlines, emphasis, and links. The goal of these tests is to ensure that Markdown operations concerning emoji are preformed in proper order, with emoji being added correctly based on other Markdown operations. See suggestion here: https://git.io/flF5W.
2018-06-21 19:40:43 +02:00
{
"name": "emoji_pipeline_newline",
"input": "The winner is:\nsmiley:smiley:",
"expected_output": "<p>The winner is:<br>\nsmiley<span class=\"emoji emoji-1f603\" title=\"smiley\">:smiley:</span></p>"
},
{
"name": "emoji_pipeline_emphasis",
"input": "Testing *:smiley*: :sm*iley*: Testing",
"expected_output": "<p>Testing <em>:smiley</em>: :sm<em>iley</em>: Testing</p>"
},
{
"name": "emoji_pipeline_link",
"input": "Visit https:smiley://google.com.",
"expected_output": "<p>Visit https<span class=\"emoji emoji-1f603\" title=\"smiley\">:smiley:</span>//google.com.</p>"
},
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
{
"name": "skin_tones_are_banned",
"input": ":skin-tone-2: :skin-tone-3:",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>:skin-tone-2: :skin-tone-3:</p>"
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
},
{
"name": "fried_egg",
"input": "new :fried_egg: emoji is banned for now.",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>new :fried_egg: emoji is banned for now.</p>"
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
},
{
"name": "emojis_with_zwj_are_banned",
"input": "Emojis like :man-girl-girl: which have ZWJ are banned for now.",
"expected_output": "<p>Emojis like :man-girl-girl: which have ZWJ are banned for now.</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Emojis like :man-girl-girl: which have ZWJ are banned for now."
build_emoji: Extend emoji mappings to use new emojis from iamcal dataset. Emojis which are represented by a sequence of codepoints or emojis with ZWJ are not included until we implement a mechanism for dealing with their unicode versions. Fixes: #6279.
2017-10-01 16:13:05 +02:00
},
[localecho] Properly escape HTML in code blocks (imported from commit 11f7e4f440cdd3a2ef6debb10c3d5a07f4fd1a1a)
2014-02-03 17:13:40 +01:00
{
"name": "safe_html",
"input": "<h1>stay normal</h1> thanks",
"expected_output": "<p>&lt;h1&gt;stay normal&lt;/h1&gt; thanks</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "<h1>stay normal<\/h1> thanks"
[localecho] Properly escape HTML in code blocks (imported from commit 11f7e4f440cdd3a2ef6debb10c3d5a07f4fd1a1a)
2014-02-03 17:13:40 +01:00
},
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
{
"name": "safe_html_with_simple_script_tag",
"input": "<script>alert(1)</script>",
"expected_output": "<p>&lt;script&gt;alert(1)&lt;/script&gt;</p>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p>&lt;script&gt;alert(1)&lt;/script&gt;\n\n</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "<script>alert(1)<\/script>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
{
"name": "safe_html_nested_script_tag",
"input": "<<script>script>evil()<</script>/script>",
"expected_output": "<p>&lt;&lt;script&gt;script&gt;evil()&lt;&lt;/script&gt;/script&gt;</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "<<script>script>evil()<<\/script>\/script>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
{
"name": "safe_html_nested_script_tag_with_parse_error",
"input": "<<x>script>evil()<</x>/script>",
"expected_output": "<p>&lt;&lt;x&gt;script&gt;evil()&lt;&lt;/x&gt;/script&gt;</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "<<x>script>evil()<<\/x>\/script>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
{
"name": "safe_html_messed_up_complexly_nested_script_tags",
"input": "<scr<script></script>ipt type=\"text/javascript\">alert(\"foo\");</<script></script>script<del></del>>",
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
"expected_output": "<p>&lt;scr&lt;script&gt;&lt;/script&gt;ipt type=\"text/javascript\"&gt;alert(\"foo\");&lt;/&lt;script&gt;&lt;/script&gt;script&lt;del&gt;&lt;/del&gt;&gt;</p>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
{
"name": "safe_html_unclosed_tag",
"input": "<script src=http://xx.com/xss.js<b>",
"expected_output": "<p>&lt;script src=http://xx.com/xss.js&lt;b&gt;</p>",
markdown: Add support for specifying marked output when not matching. This lets us document cases where the syntax is intentionally different in ways that we don't think are problematic.
2017-07-29 03:04:17 +02:00
"marked_expected_output": "<p>&lt;script src=http://xx.com/xss.js&lt;b&gt;\n\n</p>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
{
"name": "safe_html_unclosed_tag_and_quotes",
"input": "<script src=\"http://xx.com/xss.js\"<b>",
"expected_output": "<p>&lt;script src=\"http://xx.com/xss.js\"&lt;b&gt;</p>",
markdown: Add support for specifying marked output when not matching. This lets us document cases where the syntax is intentionally different in ways that we don't think are problematic.
2017-07-29 03:04:17 +02:00
"marked_expected_output": "<p>&lt;script src=&quot;http://xx.com/xss.js&quot;&lt;b&gt;\n\n</p>"
bugdown: Add tests for escaping raw html. Adds additional tests in bugdown-data.json to check that we escape raw html properly with script tags. Many of these tests are based on the bleach "advanced" test suite.
2016-10-17 22:47:52 +02:00
},
[localecho] Properly escape HTML in code blocks (imported from commit 11f7e4f440cdd3a2ef6debb10c3d5a07f4fd1a1a)
2014-02-03 17:13:40 +01:00
{
"name": "safe_html_in_code",
"input": "~~~\n<h1>stay normal</h1>",
Update Pygments to latest upstream version. In HTML, the line break immediately following a start tag is ignored (see: https://www.w3.org/TR/html4/appendix/notes.html#h-B.3.1). An extra span tag has been introduced in the upstream Pygments HtmlFormatter in order to preserve the first new line. The Bugdown Tests as well as our fenced_code.js frontend markdown processor have been updated to reflect this new behavior.
2016-09-12 20:50:10 +02:00
"expected_output": "<div class=\"codehilite\"><pre><span></span>&lt;h1&gt;stay normal&lt;/h1&gt;\n</pre></div>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "<h1>stay normal<\/h1>\n"
Add one more bugdown test (imported from commit 43b2ef02c05faf73e4607f76cd00c67e9ba38b8d)
2014-02-05 16:57:23 +01:00
},
{
"name": "ulist_with_inline_code",
"input": "gonna take a break for a bit--all yours if you want to play around too. what I did:\n\n* install cmake\n* git clone zulip desktop\n* run `cmake-gui ..` in `c:\\zulip\\zulip-desktop\\msvcbuild`\n* hit configure/generate until it generated the msvc project (had to make a fix to some cmake files)\n* opened vs2013 \n* tried to build\n",
"expected_output": "<p>gonna take a break for a bit--all yours if you want to play around too. what I did:</p>\n<ul>\n<li>install cmake</li>\n<li>git clone zulip desktop</li>\n<li>run <code>cmake-gui ..</code> in <code>c:\\zulip\\zulip-desktop\\msvcbuild</code></li>\n<li>hit configure/generate until it generated the msvc project (had to make a fix to some cmake files)</li>\n<li>opened vs2013 </li>\n<li>tried to build</li>\n</ul>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "gonna take a break for a bit--all yours if you want to play around too. what I did:\n\ninstall cmake\ngit clone zulip desktop\nrun cmake-gui .. in c:\\zulip\\zulip-desktop\\msvcbuild\nhit configure\/generate until it generated the msvc project (had to make a fix to some cmake files)\nopened vs2013 \ntried to build\n"
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
},
{
"name": "modal_link",
"input": "!modal_link(#settings, Settings page)",
bugdown: Fix modal_link. The `data-toggle` property prevented the new style of overlay modals from launching, and regardless, isn't a future-proof options for how this should work.
2017-06-03 21:36:16 +02:00
"expected_output": "<p><a href=\"#settings\" title=\"#settings\">Settings page</a></p>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p>!modal_link(#settings, Settings page)</p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "Settings page"
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
},
{
"name": "modal_link_escaped",
"input": "`!modal_link(#settings, Settings page)`",
"expected_output": "<p><code>!modal_link(#settings, Settings page)</code></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "!modal_link(#settings, Settings page)"
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
},
bugdown: Add tests for avatar/gravatar syntax.
2016-08-18 23:48:02 +02:00
{
"name": "avatar",
"input": "!avatar(username@example.com)",
"expected_output": "<p><img alt=\"username@example.com\" class=\"message_body_gravatar\" src=\"/avatar/username@example.com?s=30\" title=\"username@example.com\"></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "username@example.com"
bugdown: Add tests for avatar/gravatar syntax.
2016-08-18 23:48:02 +02:00
},
{
"name": "gravatar",
"input": "!gravatar(username@example.com)",
"expected_output": "<p><img alt=\"username@example.com\" class=\"message_body_gravatar\" src=\"/avatar/username@example.com?s=30\" title=\"username@example.com\"></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "username@example.com"
bugdown: Add tests for avatar/gravatar syntax.
2016-08-18 23:48:02 +02:00
},
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
{
"name": "avatar_escaped",
"input": "`!avatar(username@example.com)`",
"expected_output": "<p><code>!avatar(username@example.com)</code></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "!avatar(username@example.com)"
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
},
{
"name": "gravatar_escaped",
"input": "`!gravatar(username@example.com)`",
"expected_output": "<p><code>!gravatar(username@example.com)</code></p>",
tests: Add a test suite for verifying the mobile push notifs content. This test suite works by using the expected_output and new text_output fields in the bugdown test cases to verify that each syntax is correctly translated by this new function. Some of these translations, like strikethrough, are kinda poor; but this framework should make it easy to iterate on the formatting. Fixes: #6720.
2017-10-06 23:16:29 +02:00
"text_content": "!gravatar(username@example.com)"
Fix markdown ordering bugs with some custom syntax. !avatar, !modal_link, !gravatar, etc. were incorrectly being processed before the escape character for code blocks. While we're at it, we add tests for these special syntaxes.
2016-08-17 03:09:32 +02:00
},
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
{
"name": "tex_inline",
"input": "$$1 \\oplus 0 = 1$$",
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
"expected_output": "<p><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mn>1</mn><mo>⊕</mo><mn>0</mn><mo>=</mo><mn>1</mn></mrow><annotation encoding=\"application/x-tex\">1 \\oplus 0 = 1</annotation></semantics></math></span><span aria-hidden=\"true\" class=\"katex-html\"><span class=\"strut\" style=\"height:0.64444em;\"></span><span class=\"strut bottom\" style=\"height:0.72777em;vertical-align:-0.08333em;\"></span><span class=\"base\"><span class=\"mord mathrm\">1</span><span class=\"mbin\">⊕</span><span class=\"mord mathrm\">0</span><span class=\"mrel\">=</span><span class=\"mord mathrm\">1</span></span></span></span></p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_complex",
"input": "$$\\Phi_E = \\oint E \\cdot dA$$",
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
"expected_output": "<p><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><msub><mi mathvariant=\"normal\">Φ</mi><mi>E</mi></msub><mo>=</mo><mo>∮</mo><mi>E</mi><mo>⋅</mo><mi>d</mi><mi>A</mi></mrow><annotation encoding=\"application/x-tex\">\\Phi_E = \\oint E \\cdot dA</annotation></semantics></math></span><span aria-hidden=\"true\" class=\"katex-html\"><span class=\"strut\" style=\"height:0.805em;\"></span><span class=\"strut bottom\" style=\"height:1.11112em;vertical-align:-0.30612em;\"></span><span class=\"base\"><span class=\"mord\"><span class=\"mord mathrm\">Φ</span><span class=\"msupsub\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.32833099999999993em;\"><span style=\"top:-2.5500000000000003em;margin-left:0em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathit mtight\" style=\"margin-right:0.05764em;\">E</span></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.15em;\"></span></span></span></span></span><span class=\"mrel\">=</span><span class=\"mop op-symbol small-op\" style=\"margin-right:0.19445em;position:relative;top:-0.0005599999999999772em;\">∮</span><span class=\"mord mathit\" style=\"margin-right:0.05764em;\">E</span><span class=\"mbin\">⋅</span><span class=\"mord mathit\">d</span><span class=\"mord mathit\">A</span></span></span></span></p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_escaped",
"input": "`$$a$$`",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p><code>$$a$$</code></p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_fenced_math",
"input": "```math\na^2 = b^2 + c^2\n```",
bugdown: Update KaTeX to version 0.8.3 from 0.7.1. Fixes #7480.
2017-11-23 05:52:13 +01:00
"expected_output": "<p><span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><msup><mi>a</mi><mn>2</mn></msup><mo>=</mo><msup><mi>b</mi><mn>2</mn></msup><mo>+</mo><msup><mi>c</mi><mn>2</mn></msup></mrow><annotation encoding=\"application/x-tex\">a^2 = b^2 + c^2</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.8641079999999999em;\"></span><span class=\"strut bottom\" style=\"height:0.9474379999999999em;vertical-align:-0.08333em;\"></span><span class=\"base\"><span class=\"mord\"><span class=\"mord mathit\">a</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span><span class=\"mrel\">=</span><span class=\"mord\"><span class=\"mord mathit\">b</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span><span class=\"mbin\">+</span><span class=\"mord\"><span class=\"mord mathit\">c</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span></span></span></span></span></p>",
"marked_expected_output": "<span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><msup><mi>a</mi><mn>2</mn></msup><mo>=</mo><msup><mi>b</mi><mn>2</mn></msup><mo>+</mo><msup><mi>c</mi><mn>2</mn></msup></mrow><annotation encoding=\"application/x-tex\">a^2 = b^2 + c^2</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.8641079999999999em;\"></span><span class=\"strut bottom\" style=\"height:0.9474379999999999em;vertical-align:-0.08333em;\"></span><span class=\"base\"><span class=\"mord\"><span class=\"mord mathit\">a</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span><span class=\"mrel\">=</span><span class=\"mord\"><span class=\"mord mathit\">b</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span><span class=\"mbin\">+</span><span class=\"mord\"><span class=\"mord mathit\">c</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.8641079999999999em;\"><span style=\"top:-3.113em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mathrm mtight\">2</span></span></span></span></span></span></span></span></span></span></span></span>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_fenced_tex",
"input": "```tex\n\n\\pi \\textbf{ is not } 3.14\n```",
bugdown: Update KaTeX to version 0.8.3 from 0.7.1. Fixes #7480.
2017-11-23 05:52:13 +01:00
"expected_output": "<p><span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi>π</mi><mtext> is not </mtext><mn>3</mn><mi mathvariant=\"normal\">.</mi><mn>1</mn><mn>4</mn></mrow><annotation encoding=\"application/x-tex\">\n\\pi \\textbf{ is not } 3.14</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.69444em;\"></span><span class=\"strut bottom\" style=\"height:0.69444em;vertical-align:0em;\"></span><span class=\"base\"><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">π</span><span class=\"mord text\"><span class=\"mord mathrm\"> </span><span class=\"mord mathbf\">is</span><span class=\"mord mathrm\"> </span><span class=\"mord mathbf\">not</span><span class=\"mord mathrm\"> </span></span><span class=\"mord mathrm\">3</span><span class=\"mord mathrm\">.</span><span class=\"mord mathrm\">1</span><span class=\"mord mathrm\">4</span></span></span></span></span></p>",
"marked_expected_output": "<span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi>π</mi><mtext> is not </mtext><mn>3</mn><mi mathvariant=\"normal\">.</mi><mn>1</mn><mn>4</mn></mrow><annotation encoding=\"application/x-tex\">\n\\pi \\textbf{ is not } 3.14</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.69444em;\"></span><span class=\"strut bottom\" style=\"height:0.69444em;vertical-align:0em;\"></span><span class=\"base\"><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">π</span><span class=\"mord text\"><span class=\"mord mathrm\"> </span><span class=\"mord mathbf\">is</span><span class=\"mord mathrm\"> </span><span class=\"mord mathbf\">not</span><span class=\"mord mathrm\"> </span></span><span class=\"mord mathrm\">3</span><span class=\"mord mathrm\">.</span><span class=\"mord mathrm\">1</span><span class=\"mord mathrm\">4</span></span></span></span></span>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_fenced_latex",
"input": "```latex\n\n\\frac{1}{\\sqrt{2}}\n\\begin{bmatrix}\n1 & 1 \\\\\n1 & -1\n\\end{bmatrix}\n```",
bugdown: Update KaTeX to version 0.8.3 from 0.7.1. Fixes #7480.
2017-11-23 05:52:13 +01:00
"expected_output": "<p><span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mfrac><mrow><mn>1</mn></mrow><mrow><msqrt><mrow><mn>2</mn></mrow></msqrt></mrow></mfrac><mrow><mo fence=\"true\">[</mo><mtable><mtr><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd></mtr><mtr><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mo>−</mo><mn>1</mn></mrow></mstyle></mtd></mtr></mtable><mo fence=\"true\">]</mo></mrow></mrow><annotation encoding=\"application/x-tex\">\n\\frac{1}{\\sqrt{2}}\n\\begin{bmatrix}\n1 &amp; 1 \\\\\n1 &amp; -1\n\\end{bmatrix}</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:1.45em;\"></span><span class=\"strut bottom\" style=\"height:2.40003em;vertical-align:-0.95003em;\"></span><span class=\"base\"><span class=\"mord\"><span class=\"mopen nulldelimiter\"></span><span class=\"mfrac\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.32144em;\"><span style=\"top:-2.2027799999999997em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord sqrt\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist svg-align\" style=\"height:0.90722em;\"><span style=\"top:-3em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\" style=\"padding-left:0.833em;\"><span class=\"mord mathrm\">2</span></span></span><span style=\"top:-2.86722em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span style=\"height:1em;\"><svg width='100%' height='1em'>\n <svg viewBox='0 0 400000 1000' preserveAspectRatio='xMinYMin\nslice'><path d='M95 622c-2.667 0-7.167-2.667-13.5\n-8S72 604 72 600c0-2 .333-3.333 1-4 1.333-2.667 23.833-20.667 67.5-54s\n65.833-50.333 66.5-51c1.333-1.333 3-2 5-2 4.667 0 8.667 3.333 12 10l173\n378c.667 0 35.333-71 104-213s137.5-285 206.5-429S812 17.333 812 14c5.333\n-9.333 12-14 20-14h399166v40H845.272L620 507 385 993c-2.667 4.667-9 7-19\n7-6 0-10-1-12-3L160 575l-65 47zM834 0h399166v40H845z'/></svg></svg></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.13278em;\"></span></span></span></span></span></span><span style=\"top:-3.23em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"frac-line\" style=\"border-bottom-width:0.04em;\"></span></span><span style=\"top:-3.677em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.93em;\"></span></span></span></span><span class=\"mclose nulldelimiter\"></span></span><span class=\"minner\"><span class=\"mopen delimcenter\" style=\"top:0em;\"><span class=\"delimsizing size3\">[</span></span><span class=\"mord\"><span class=\"mtable\"><span class=\"col-align-c\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.45em;\"><span style=\"top:-3.61em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span><span style=\"top:-2.4099999999999997em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.9500000000000004em;\"></span></span></span></span><span class=\"arraycolsep\" style=\"width:0.5em;\"></span><span class=\"arraycolsep\" style=\"width:0.5em;\"></span><span class=\"col-align-c\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.45em;\"><span style=\"top:-3.61em;
"marked_expected_output": "<span class=\"katex-display\"><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mfrac><mrow><mn>1</mn></mrow><mrow><msqrt><mrow><mn>2</mn></mrow></msqrt></mrow></mfrac><mrow><mo fence=\"true\">[</mo><mtable><mtr><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd></mtr><mtr><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mn>1</mn></mrow></mstyle></mtd><mtd><mstyle scriptlevel=\"0\" displaystyle=\"false\"><mrow><mo>−</mo><mn>1</mn></mrow></mstyle></mtd></mtr></mtable><mo fence=\"true\">]</mo></mrow></mrow><annotation encoding=\"application/x-tex\">\n\\frac{1}{\\sqrt{2}}\n\\begin{bmatrix}\n1 &amp; 1 \\\\\n1 &amp; -1\n\\end{bmatrix}</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:1.45em;\"></span><span class=\"strut bottom\" style=\"height:2.40003em;vertical-align:-0.95003em;\"></span><span class=\"base\"><span class=\"mord\"><span class=\"mopen nulldelimiter\"></span><span class=\"mfrac\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.32144em;\"><span style=\"top:-2.2027799999999997em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord sqrt\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist svg-align\" style=\"height:0.90722em;\"><span style=\"top:-3em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\" style=\"padding-left:0.833em;\"><span class=\"mord mathrm\">2</span></span></span><span style=\"top:-2.86722em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span style=\"height:1em;\"><svg width='100%' height='1em'>\n <svg viewBox='0 0 400000 1000' preserveAspectRatio='xMinYMin\nslice'><path d='M95 622c-2.667 0-7.167-2.667-13.5\n-8S72 604 72 600c0-2 .333-3.333 1-4 1.333-2.667 23.833-20.667 67.5-54s\n65.833-50.333 66.5-51c1.333-1.333 3-2 5-2 4.667 0 8.667 3.333 12 10l173\n378c.667 0 35.333-71 104-213s137.5-285 206.5-429S812 17.333 812 14c5.333\n-9.333 12-14 20-14h399166v40H845.272L620 507 385 993c-2.667 4.667-9 7-19\n7-6 0-10-1-12-3L160 575l-65 47zM834 0h399166v40H845z'/></svg></svg></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.13278em;\"></span></span></span></span></span></span><span style=\"top:-3.23em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"frac-line\" style=\"border-bottom-width:0.04em;\"></span></span><span style=\"top:-3.677em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.93em;\"></span></span></span></span><span class=\"mclose nulldelimiter\"></span></span><span class=\"minner\"><span class=\"mopen delimcenter\" style=\"top:0em;\"><span class=\"delimsizing size3\">[</span></span><span class=\"mord\"><span class=\"mtable\"><span class=\"col-align-c\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.45em;\"><span style=\"top:-3.61em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span><span style=\"top:-2.4099999999999997em;\"><span class=\"pstrut\" style=\"height:3em;\"></span><span class=\"mord\"><span class=\"mord mathrm\">1</span></span></span></span><span class=\"vlist-s\">​</span></span><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.9500000000000004em;\"></span></span></span></span><span class=\"arraycolsep\" style=\"width:0.5em;\"></span><span class=\"arraycolsep\" style=\"width:0.5em;\"></span><span class=\"col-align-c\"><span class=\"vlist-t vlist-t2\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:1.45em;\"><span style=\"top:-3.6
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_money",
"input": "Tickets are $5 to $20 for youth, $10-$30 for adults, so we are hoping to bring in $500 from the event ($$x \\approx 500\\$$$)",
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
"expected_output": "<p>Tickets are $5 to $20 for youth, $10-$30 for adults, so we are hoping to bring in $500 from the event (<span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi>x</mi><mo>≈</mo><mn>5</mn><mn>0</mn><mn>0</mn><mi mathvariant=\"normal\">$</mi></mrow><annotation encoding=\"application/x-tex\">x \\approx 500\\$</annotation></semantics></math></span><span aria-hidden=\"true\" class=\"katex-html\"><span class=\"strut\" style=\"height:0.75em;\"></span><span class=\"strut bottom\" style=\"height:0.80556em;vertical-align:-0.05556em;\"></span><span class=\"base\"><span class=\"mord mathit\">x</span><span class=\"mrel\">≈</span><span class=\"mord mathrm\">5</span><span class=\"mord mathrm\">0</span><span class=\"mord mathrm\">0</span><span class=\"mord mathrm\">$</span></span></span></span>)</p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
lint: Ban tab-based whitespace in our our text fixtures. We don't want to do this for the webhook fixtures since those come from third-party code, but it makes sense to do this for hand-edited code.
2017-11-23 19:39:58 +01:00
{
"name": "tex_inline_permissive_spacing",
"input": "$$ x = 7 $$",
node tests: Compare markdown using semantic equivalence. Fix #4367
2017-12-10 09:01:37 +01:00
"expected_output": "<p><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mi>x</mi><mo>=</mo><mn>7</mn></mrow><annotation encoding=\"application/x-tex\"> x = 7 </annotation></semantics></math></span><span aria-hidden=\"true\" class=\"katex-html\"><span class=\"strut\" style=\"height:0.64444em;\"></span><span class=\"strut bottom\" style=\"height:0.64444em;vertical-align:0em;\"></span><span class=\"base\"><span class=\"mord mathit\">x</span><span class=\"mrel\">=</span><span class=\"mord mathrm\">7</span></span></span></span></p>"
lint: Ban tab-based whitespace in our our text fixtures. We don't want to do this for the webhook fixtures since those come from third-party code, but it makes sense to do this for hand-edited code.
2017-11-23 19:39:58 +01:00
},
{
"name": "tex_inline_prohibited_newline",
"input": "$$x=3\ny=4$$",
"expected_output": "<p>$$x=3<br>\ny=4$$</p>"
},
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
{
"name": "tex_dollar_smiley",
"input": "$$_$$ is a fun money-related smiley!",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>$$_$$ is a fun money-related smiley!</p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_multiple_dollars",
"input": "We are going to make some $$$ or maybe even $$$$!",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>We are going to make some $$$ or maybe even $$$$!</p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_non_matching_dollar_count",
"input": "$foo is$$",
markdown: Remove now-obsolete bugdown_matches_marked. Fixes #7099.
2017-11-07 21:01:57 +01:00
"expected_output": "<p>$foo is$$</p>"
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_safe_script_tag",
"input": "$$<script type='text/javascript'>alert('xss');</script>$$\n\n~~~math\n<script type='text/javascript'>alert('xss');</script>\n~~~",
bugdown: Update KaTeX to version 0.8.3 from 0.7.1. Fixes #7480.
2017-11-23 05:52:13 +01:00
"expected_output": "<p><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mo>&lt;</mo><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><mi>t</mi><mi>t</mi><mi>y</mi><mi>p</mi><mi>e</mi><msup><mo>=</mo><mo mathvariant=\"normal\">′</mo></msup><mi>t</mi><mi>e</mi><mi>x</mi><mi>t</mi><mi mathvariant=\"normal\">/</mi><mi>j</mi><mi>a</mi><mi>v</mi><mi>a</mi><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><msup><mi>t</mi><mo mathvariant=\"normal\">′</mo></msup><mo>&gt;</mo><mi>a</mi><mi>l</mi><mi>e</mi><mi>r</mi><mi>t</mi><msup><mo>(</mo><mo mathvariant=\"normal\">′</mo></msup><mi>x</mi><mi>s</mi><msup><mi>s</mi><mo mathvariant=\"normal\">′</mo></msup><mo>)</mo><mo separator=\"true\">;</mo><mo>&lt;</mo><mi mathvariant=\"normal\">/</mi><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><mi>t</mi><mo>&gt;</mo></mrow><annotation encoding=\"application/x-tex\">&lt;script type='text/javascript'&gt;alert('xss');&lt;/script&gt;</annotation></semantics></math></span><span aria-hidden=\"true\" class=\"katex-html\"><span class=\"strut\" style=\"height:0.751892em;\"></span><span class=\"strut bottom\" style=\"height:1.001892em;vertical-align:-0.25em;\"></span><span class=\"base\"><span class=\"mrel\">&lt;</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\">c</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">i</span><span class=\"mord mathit\">p</span><span class=\"mord mathit\">t</span><span class=\"mord mathit\">t</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">y</span><span class=\"mord mathit\">p</span><span class=\"mord mathit\">e</span><span class=\"mrel\"><span class=\"mrel\">=</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mord mathit\">t</span><span class=\"mord mathit\">e</span><span class=\"mord mathit\">x</span><span class=\"mord mathit\">t</span><span class=\"mord mathrm\">/</span><span class=\"mord mathit\" style=\"margin-right:0.05724em;\">j</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">v</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\">c</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">i</span><span class=\"mord mathit\">p</span><span class=\"mord\"><span class=\"mord mathit\">t</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mrel\">&gt;</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.01968em;\">l</span><span class=\"mord mathit\">e</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">t</span><span class=\"mopen\"><span class=\"mopen\">(</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mord mathit\">x</span><span class=\"mord mathit\">s</span><span class=\"mord\"><span class=\"mord mathit\">s</span><span class=\"msupsub\"><spa
"marked_expected_output": "<p><span class=\"katex\"><span class=\"katex-mathml\"><math><semantics><mrow><mo>&lt;</mo><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><mi>t</mi><mi>t</mi><mi>y</mi><mi>p</mi><mi>e</mi><msup><mo>=</mo><mo mathvariant=\"normal\">′</mo></msup><mi>t</mi><mi>e</mi><mi>x</mi><mi>t</mi><mi mathvariant=\"normal\">/</mi><mi>j</mi><mi>a</mi><mi>v</mi><mi>a</mi><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><msup><mi>t</mi><mo mathvariant=\"normal\">′</mo></msup><mo>&gt;</mo><mi>a</mi><mi>l</mi><mi>e</mi><mi>r</mi><mi>t</mi><msup><mo>(</mo><mo mathvariant=\"normal\">′</mo></msup><mi>x</mi><mi>s</mi><msup><mi>s</mi><mo mathvariant=\"normal\">′</mo></msup><mo>)</mo><mo separator=\"true\">;</mo><mo>&lt;</mo><mi mathvariant=\"normal\">/</mi><mi>s</mi><mi>c</mi><mi>r</mi><mi>i</mi><mi>p</mi><mi>t</mi><mo>&gt;</mo></mrow><annotation encoding=\"application/x-tex\">&lt;script type=&#x27;text/javascript&#x27;&gt;alert(&#x27;xss&#x27;);&lt;/script&gt;</annotation></semantics></math></span><span class=\"katex-html\" aria-hidden=\"true\"><span class=\"strut\" style=\"height:0.751892em;\"></span><span class=\"strut bottom\" style=\"height:1.001892em;vertical-align:-0.25em;\"></span><span class=\"base\"><span class=\"mrel\">&lt;</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\">c</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">i</span><span class=\"mord mathit\">p</span><span class=\"mord mathit\">t</span><span class=\"mord mathit\">t</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">y</span><span class=\"mord mathit\">p</span><span class=\"mord mathit\">e</span><span class=\"mrel\"><span class=\"mrel\">=</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mord mathit\">t</span><span class=\"mord mathit\">e</span><span class=\"mord mathit\">x</span><span class=\"mord mathit\">t</span><span class=\"mord mathrm\">/</span><span class=\"mord mathit\" style=\"margin-right:0.05724em;\">j</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.03588em;\">v</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\">s</span><span class=\"mord mathit\">c</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">i</span><span class=\"mord mathit\">p</span><span class=\"mord\"><span class=\"mord mathit\">t</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mrel\">&gt;</span><span class=\"mord mathit\">a</span><span class=\"mord mathit\" style=\"margin-right:0.01968em;\">l</span><span class=\"mord mathit\">e</span><span class=\"mord mathit\" style=\"margin-right:0.02778em;\">r</span><span class=\"mord mathit\">t</span><span class=\"mopen\"><span class=\"mopen\">(</span><span class=\"msupsub\"><span class=\"vlist-t\"><span class=\"vlist-r\"><span class=\"vlist\" style=\"height:0.751892em;\"><span style=\"top:-3.063em;margin-right:0.05em;\"><span class=\"pstrut\" style=\"height:2.7em;\"></span><span class=\"sizing reset-size6 size3 mtight\"><span class=\"mord mtight\"><span class=\"mord mathrm mtight\">′</span></span></span></span></span></span></span></span></span><span class=\"mord mathit\">x</span><span class=\"mord mathit\">s</span><span class=\"mord\"><span class=\"mord mathit\">s</span><
markdown: Add TeX typesetting support. Co-authored-by: Reid Barton <rwbarton@gmail.com> Fixes #2056.
2017-03-20 16:56:39 +01:00
},
{
"name": "tex_error_safe_script_tag",
"input": "$$\\<script type='text/javascript'>alert('xss');</script>$$\n\n~~~math\n\\<script type='text/javascript'>alert('xss');</script>\n~~~",
"expected_output": "<p><span class=\"tex-error\">$$\\&lt;script type='text/javascript'&gt;alert('xss');&lt;/script&gt;$$</span></p>\n<p><span class=\"tex-error\">\\&lt;script type=&#39;text/javascript&#39;&gt;alert(&#39;xss&#39;);&lt;/script&gt;</span></p>",
markdown_test_cases: Clean cases where bugdown_matches_marked is false. Fixes #7099.
2017-11-02 16:30:36 +01:00
"marked_expected_output": "<p><span class=\"tex-error\">$$\\&lt;script type=&#39;text/javascript&#39;&gt;alert(&#39;xss&#39;);&lt;/script&gt;$$</span></p>\n<span class=\"tex-error\">\\&lt;script type=&#39;text/javascript&#39;&gt;alert(&#39;xss&#39;);&lt;/script&gt;</span>"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
}
],
"linkify_tests": [
[
"http://www.google.com",
"<p>%s</p>",
"http://www.google.com"
],
[
"https://www.google.com",
"<p>%s</p>",
"https://www.google.com"
],
[
"http://www.theregister.co.uk/foo/bar",
"<p>%s</p>",
"http://www.theregister.co.uk/foo/bar"
],
[
" some text https://www.google.com/",
"<p>some text %s</p>",
"https://www.google.com/"
],
[
"with short example.com url",
"<p>with short %s url</p>",
"example.com"
],
[
"t.co",
"<p>%s</p>",
"t.co"
],
bugdown: Blacklist linkifying the .md TLD. Fixes #2065.
2016-12-30 03:15:48 +01:00
[
"readme.md",
"<p>readme.md</p>",
"readme.md"
],
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
[
"go to views.org please",
"<p>go to %s please</p>",
"views.org"
],
[
"http://foo.com/blah_blah/",
"<p>%s</p>",
"http://foo.com/blah_blah/"
],
[
"python class views.py is",
"<p>python class views.py is</p>",
""
],
[
"with www www.zulip.com/foo ok?",
"<p>with www %s ok?</p>",
"www.zulip.com/foo"
],
[
"allow questions like foo.com?",
"<p>allow questions like %s?</p>",
"foo.com"
],
[
"\"is.gd/foo/ \"",
"<p>\"%s \"</p>",
"is.gd/foo/"
],
[
"end of sentence https://t.co.",
"<p>end of sentence %s.</p>",
"https://t.co"
],
[
"(Something like http://foo.com/blah_blah)",
"<p>(Something like %s)</p>",
"http://foo.com/blah_blah"
],
[
"\"is.gd/foo/\"",
"<p>\"%s\"</p>",
"is.gd/foo/"
],
[
"end with a quote www.google.com\"",
"<p>end with a quote %s\"</p>",
"www.google.com"
],
Allow auto-linked URLs to end with a !, without including the ! in the url (imported from commit 26fbf8d8318dc32f31f94f366750521afab94ac5)
2014-03-05 21:17:48 +01:00
[
"end with an exclamation www.google.com!",
"<p>end with an exclamation %s!</p>",
"www.google.com"
],
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
[
"http://www.guardian.co.uk/foo/bar",
"<p>%s</p>",
"http://www.guardian.co.uk/foo/bar"
],
[
"from http://supervisord.org/running.html:",
"<p>from %s:</p>",
"http://supervisord.org/running.html"
],
[
"http://raven.io",
"<p>%s</p>",
"http://raven.io"
],
[
"at https://zulip.com/api. Check it!",
"<p>at %s. Check it!</p>",
"https://zulip.com/api"
],
[
"goo.gl/abc",
"<p>%s</p>",
"goo.gl/abc"
],
[
"I spent a year at ucl.ac.uk",
"<p>I spent a year at %s</p>",
"ucl.ac.uk"
],
[
"http://a.cc/i/FMXO",
"<p>%s</p>",
"http://a.cc/i/FMXO"
],
[
"http://fmota.eu/blog/test.html",
"<p>%s</p>",
"http://fmota.eu/blog/test.html"
],
[
"http://j.mp/14Hwm3X",
"<p>%s</p>",
"http://j.mp/14Hwm3X"
],
[
"http://localhost:9991/?show_debug=1",
"<p>%s</p>",
"http://localhost:9991/?show_debug=1"
],
[
"anyone before? (http://a.cc/i/FMXO)",
"<p>anyone before? (%s)</p>",
"http://a.cc/i/FMXO"
],
[
"(http://en.wikipedia.org/wiki/Each-way_(bet))",
"<p>(%s)</p>",
"http://en.wikipedia.org/wiki/Each-way_(bet)"
],
[
"(http://en.wikipedia.org/wiki/Each-way_(bet)_(more_parens))",
"<p>(%s)</p>",
"http://en.wikipedia.org/wiki/Each-way_(bet)_(more_parens)"
],
[
"http://en.wikipedia.org/wiki/Qt_(framework)",
"<p>%s</p>",
"http://en.wikipedia.org/wiki/Qt_(framework)"
],
[
"http://fr.wikipedia.org/wiki/Fichier:SMirC-facepalm.svg",
"<p>%s</p>",
"http://fr.wikipedia.org/wiki/Fichier:SMirC-facepalm.svg"
],
[
"https://en.wikipedia.org/wiki/File:Methamphetamine_from_ephedrine_with_HI_en.mov",
"<p>%s</p>",
"https://en.wikipedia.org/wiki/File:Methamphetamine_from_ephedrine_with_HI_en.mov"
],
[
"https://jira.atlassian.com/browse/JRA-31953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel",
"<p>%s</p>",
"https://jira.atlassian.com/browse/JRA-31953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel"
],
[
"http://web.archive.org/web/20120630032016/http://web.mit.edu/mitcard/idpolicies.html",
"<p>%s</p>",
"http://web.archive.org/web/20120630032016/http://web.mit.edu/mitcard/idpolicies.html"
],
[
"http://www.postgresql.org/message-id/14040.1364490185@sss.pgh.pa.us",
"<p>%s</p>",
"http://www.postgresql.org/message-id/14040.1364490185@sss.pgh.pa.us"
],
[
"javascript:alert(\"hi\");.com",
"<p>javascript:alert(\"hi\");.com</p>",
""
],
[
"javascript:foo.com",
"<p>javascript:%s</p>",
"foo.com"
],
[
"javascript://foo.com",
"<p>javascript://foo.com</p>",
""
],
[
"foobarscript://foo.com",
"<p>foobarscript://foo.com</p>",
""
],
[
"about:blank.com",
"<p>about:%s</p>",
"blank.com"
],
[
"[foo](javascript:foo.com)",
"<p>[foo](javascript:%s)</p>",
"foo.com"
],
[
"[foo](javascript://foo.com)",
"<p>[foo](javascript://foo.com)</p>",
""
],
[
"aim:addbuddy?screenname=foo",
"<p>aim:addbuddy?screenname=foo</p>",
""
],
[
"itms://itunes.com/apps/appname",
"<p>itms://itunes.com/apps/appname</p>",
""
],
[
"[foo](itms://itunes.com/apps/appname)",
"<p>[foo](itms://itunes.com/apps/appname)</p>",
""
],
[
"1 [](foo://) 3 [](foo://) 5",
"<p>1 [](foo://) 3 [](foo://) 5</p>",
""
],
[
"javascript:<i>\"foo&bar\"</i>",
"<p>javascript:&lt;i&gt;\"foo&amp;bar\"&lt;/i&gt;</p>",
""
],
[
"[foo](javascript:<i>\"foo&bar\"</i>)",
"<p>[foo](javascript:&lt;i&gt;\"foo&amp;bar\"&lt;/i&gt;)</p>",
""
],
[
"a@b.com",
"<p>%s</p>",
"a@b.com"
],
[
"<a@b.com>",
"<p>&lt;%s&gt;</p>",
"a@b.com"
],
[
"a@b.com/foo",
"<p>a@b.com/foo</p>",
""
],
[
"http://leo@foo.com/my/file",
"<p>%s</p>",
"http://leo@foo.com/my/file"
],
[
"http://example.com/something?with,commas,in,url, but not at end",
"<p>%s, but not at end</p>",
"http://example.com/something?with,commas,in,url"
],
[
"http://www.yelp.com/biz/taim-mobile-falafel-and-smoothie-truck-new-york#query",
"<p>%s</p>",
"http://www.yelp.com/biz/taim-mobile-falafel-and-smoothie-truck-new-york#query"
],
[
" some text https://www.google.com/baz_(match)?with=foo&bar=baz with extras",
"<p>some text %s with extras</p>",
"https://www.google.com/baz_(match)?with=foo&amp;bar=baz"
],
[
"hash it http://foo.com/blah_(wikipedia)_blah#cite-1",
"<p>hash it %s</p>",
"http://foo.com/blah_(wikipedia)_blah#cite-1"
],
[
"http://technet.microsoft.com/en-us/library/Cc751099.rk20_25_big(l=en-us).mov",
"<p>%s</p>",
"http://technet.microsoft.com/en-us/library/Cc751099.rk20_25_big(l=en-us).mov"
],
[
"https://metacpan.org/module/Image::Resize::OpenCV",
"<p>%s</p>",
"https://metacpan.org/module/Image::Resize::OpenCV"
],
[
"foo.com/a::trollface::b",
"<p>%s</p>",
"foo.com/a::trollface::b"
],
[
"a.commandstuff()",
"<p>a.commandstuff()</p>",
""
],
[
"love...it",
"<p>love...it</p>",
""
],
[
"sorry,http://example.com/",
"<p>sorry,%s</p>",
"http://example.com/"
bugdown: Match up to 8 groups of nested parens (imported from commit e3d61ec644fdb293322cab0a4449d8e1a27a513a)
2014-02-06 23:07:24 +01:00
],
[
"two nested parens https://zulip.com/(we_like_(to_nest_)_nest)_nest",
"<p>two nested parens %s</p>",
"https://zulip.com/(we_like_(to_nest_)_nest)_nest"
],
[
"three nested parens https://zulip.com/(we_like_(to_(and_)nest_)_nest)_nest",
"<p>three nested parens %s</p>",
"https://zulip.com/(we_like_(to_(and_)nest_)_nest)_nest"
],
[
"four nested parens https://zulip.com/(we_like_(to_n(e)st_)_n(es)t)_nest",
"<p>four nested parens %s</p>",
"https://zulip.com/(we_like_(to_n(e)st_)_n(es)t)_nest"
],
[
"six nested parens https://zulip.com/(we_like_((t(d(o(___)o)o))o_nest_)_nest)_nest",
"<p>six nested parens %s</p>",
"https://zulip.com/(we_like_((t(d(o(___)o)o))o_nest_)_nest)_nest"
],
[
"eight is too many https://zulip.com/(we_like_((t(d(o(_(1(2)1)__)o)o))o_nest_)_nest)_nest",
"<p>eight is too many https://zulip.com/(we_like_((t(d(o(_(1(2)1)__)o)o))o_nest_)_nest)_nest</p>",
""
],
[
"nested with autodetection zulip.us/(we_like_(to_n(e)st_)_n(es)t)_nest",
"<p>nested with autodetection %s</p>",
"zulip.us/(we_like_(to_n(e)st_)_n(es)t)_nest"
],
[
"quora http://generate.quora.net/render?width=700&from=-4hours&until=now&height=400&bgcolor=black&lineMode=connected&title=arb%20hint%20status&target=alias(ans.hintland.hand.arb.enhint_rate%2C%22enhint%20rate%22)&target=alias(ans.hintland.hand.arb.unhint_rate%2C%22unhint%20rate%22)&target=alias(ans.hintland.hand.arb.size%2C%22hint%20size%22)&target=alias(scale(ans.vagabond.dingarb_cube_count%2C10000)%2C%22cube%20count%20x%2010K%22)&target=alias(scale(hnumbers.time.ding.gegevens.query.count%2C10)%2C%22ding%20gegevens%20query%20count%20x%2010%22)&fgcolor=white&uniq=0.44046106841415167",
"<p>quora %s</p>",
"http://generate.quora.net/render?width=700&amp;from=-4hours&amp;until=now&amp;height=400&amp;bgcolor=black&amp;lineMode=connected&amp;title=arb%20hint%20status&amp;target=alias(ans.hintland.hand.arb.enhint_rate%2C%22enhint%20rate%22)&amp;target=alias(ans.hintland.hand.arb.unhint_rate%2C%22unhint%20rate%22)&amp;target=alias(ans.hintland.hand.arb.size%2C%22hint%20size%22)&amp;target=alias(scale(ans.vagabond.dingarb_cube_count%2C10000)%2C%22cube%20count%20x%2010K%22)&amp;target=alias(scale(hnumbers.time.ding.gegevens.query.count%2C10)%2C%22ding%20gegevens%20query%20count%20x%2010%22)&amp;fgcolor=white&amp;uniq=0.44046106841415167"
Share bugdown test data across frontend and backend tests (imported from commit b278a60b5899cd336840e71d8e632e2b31338d82)
2014-01-17 21:08:45 +01:00
]
]
Tolerate spaces after language in markdown fences. See #2357. We now support `~~~ .py ` with that trailing space. Note that the test coverage is Python-side only due to bugdown_matches_marked being set to false, since we don't yet support language syntax on the client side. (imported from commit ccd5fcb0eee01478d349161400103480678d7486)
2014-03-06 00:05:49 +01:00
}