Using markdown when opening a bug report does not work.

Fixed Issue #7220390

Details

Created
Apr 15, 2016
Privacy
This issue is public.
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

This is the Markdown example:

Remarkable

Experience real-time editing with Remarkable!
Click the clear link to start with a clean slate, or get the permalink to share or save your results.


h1 Heading

h2 Heading

h3 Heading

h4 Heading

h5 Heading
h6 Heading

Horizontal Rules




Typographic replacements

Enable typographer option to see result.
© © ® ® ™ ™ § § ±
test… test… test… test?.. test!..
!!! ??? ,
Remarkable – awesome
“Smartypants, double quotes”
‘Smartypants, single quotes’

Emphasis

This is bold text
This is bold text
This is italic text
This is italic text
Deleted text
Superscript: 19th
Subscript: H2O
Inserted text
Marked text

Blockquotes

Blockquotes can also be nested…

…by using additional greater-than signs right next to each other…

…or with spaces between arrows.

Lists

Unordered

  • Create a list by starting a line with +, -, or *
  • Sub-lists are made by indenting 2 spaces:
    • Marker character change forces new list start:
      • Ac tristique libero volutpat at
      • Facilisis in pretium nisl aliquet
      • Nulla volutpat aliquam velit
  • Very easy!
    Ordered
  1. Lorem ipsum dolor sit amet
  2. Consectetur adipiscing elit
  3. Integer molestie lorem at massa
  4. You can use sequential numbers…
  5. …or keep all the numbers as 1.
    Start numbering with offset:
  6. foo
  7. bar

Code

Inline code
Indented code
// Some comments
line 1 of code
line 2 of code
line 3 of code
Block code “fences”

Sample text here...

Syntax highlighting

var foo = function (bar) {
  return bar++;
};
console.log(foo(5));

Tables

OptionDescription
datapath to data files to supply the data that will be passed into templates.
engineengine to be used for processing templates. Handlebars is the default.
extextension to be used for dest files.

Right aligned columns

OptionDescription
datapath to data files to supply the data that will be passed into templates.
engineengine to be used for processing templates. Handlebars is the default.
extextension to be used for dest files.

Links

link text
link with title
Autoconverted link https://github.com/nodeca/pica (enable linkify to see)

Images

Minion
Stormtroopocat
Like links, Images also have a footnote style syntax
![Alt text][id]
With a reference later in the document defining the URL location:
[id]: https://octodex.github.com/images/dojocat.jpg “The Dojocat”

Footnotes

Footnote 1 link[1].
Footnote 2 link[2].
Inline footnote[3] definition.
Duplicated footnote reference[2].

Definition lists

Term 1
Definition 1
with lazy continuation.
Term 2 with inline markup
Definition 2
{ some code, part of Definition 2 }
Third paragraph of definition 2.
Compact style:
Term 1 ~ Definition 1
Term 2
~ Definition 2a
Definition 2b

Abbreviations

This is HTML abbreviation example.
It converts "HTML", but keep intact partial entries like “xxxHTMLyyy” and so on.
*[HTML]: Hyper Text Markup Language


Advertisement :)

  • pica - high quality and fast image
    resize in browser.
  • babelfish - developer friendly
    i18n with plurals support and easy syntax.
    You’ll like those projects! :)

  1. Footnote can have markup
    and multiple paragraphs.

  2. Footnote text.

  3. Text of inline footnote

Attachments

0 attachments

    Comments and activity

    • As you can see, this looks nothing like https://jonschlinkert.github.io/remarkable/demo/ - only a subset of Markdown is supported.

    • I’ve noticed this too. Supporting just a subset of markdown isn’t a big deal, but the one that’s really painful is that Bullet and Numbered lists specifically do not terminate after a blank line.

      For example:

      • Bullet
      • List

      This sentence is 2 lines below the final “List” bullet, which should terminate the . The preview tab does this properly. Yet when I submit, this sentence will appear as part of the final bullet. Please fix :)

      Thanks! <-- Also 2 lines down from the previous sentence.

    • ^^ Hmmm… That’s interesting. Seems to work properly in comments. Just not when opening a bug.

    • Yes, hence the title :)

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • Since this looks okay now, I am assuming this has been corrected. The item is now being closed out.

      Thanks for the feedback and patience with our new issue tracker.

      All the best,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Hi Brad,

      Have you actually tested it?

      https://www.youtube.com/watch?v=wg4trPZFUwc

    • Microsoft Edge Team

      Changed Assigned To to “Anton M.”

      Changed Status from “Not reproducible” to “Confirmed”

    • We are working on improving our markdown support. Repro steps is an editable field in VSO, and VSO also adds some HTML on its side so this is a bit more complicated than we would like to :(
      We use remarkable on our side so we should make it happen.

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • I had to enable a couple more features in remarkable to make everything work but it looks like it is working as expected now.

    You need to sign in to your Microsoft account to add a comment.

    Sign in