attribute explanations should be treated as markdown (I think) about js-doc-parse

[ttrenka]

I think your assumption is wrong; from what I'm reading in the 1.6 details.xml file, all of those are assumed to be summaries (i.e. <summary> elements), which are not Markdown enabled.

Pretty sure you can't include examples in there as well (at least with the old parser).

[wkeese]

Ugh, @ttrenka you are right... so does that mean that this is also invalid?

// textDir: String
//      Bi-directional support, the main variable which is responsible for the direction of the text.
//      The text direction can be different than the GUI direction by using this parameter in creation
//      of a widget.
//      Allowed values:
//          1. "ltr"
//          2. "rtl"
//          3. "auto" - contextual the direction of a text defined by first strong letter.
//      By default is as the page direction.

(because the numbered list will be smushed into plain text)

[csnover]

I’m happy to just throw most everything through the markdown parser at this point if you want. Seems like nobody paid attention to the fact that they can’t use markdown everywhere…

[wkeese]

I'm in favor of parsing everything as markdown assuming @ttrenka, @cjolif etc. don't have any strong objections... it seems like markdown is mostly backwards-compatible with plain text. Probably there are some theoretical cases where parsing attributes and summary as markdown could break something, but I don't think it would be a big issue in practice.