Thanks all, I've spoken with support and opened a ticket. The problem is largely in the Webex Windows app. Messages rendered through the web.webex.com web portal (left side) and Webex Windows app (right side) are not consistent. The top of each screen cap was sent through the web app (it's the same source text/message on the left and right), the bottom message in each cap was sent through the Windows app ((it's the same source text/message on the left and right).
I don't know about anyone else, but I found it hard to see the difference between the consistently broken and the consistently render as expected, so I asked Atom to help:
The consistently broken is on top the consistently render as expected on the bottom
Oh - I've just noticed you hid an attachment too. Let's reveal that so we can all see it.
Now @B Herron , you say "emitting markdown messages containing URLs" - so I assume you are entering these in markdown. As in
```https://AServer.ADomain.com/tfs/BrianCollection/BrianProject/_git/arg/pullrequest/26``` ```https://AServer.ADomain.com/tfs/BrianCollection/BrianProject/_git/arg/pullrequest/26```
in which case I'd expect that NO link is created - is that what you want?
What you wrote is a code snippet, that’s not what the OP referenced if I understand that post correctly.
So I take your point - I probably should have put a picture from Webex - like this:
I wanted to emphasise the markdown text, so I displayed on this forum inside <pre></pre> tags (which are often referred to as code snippets, which are actually written inside <code></code> tags on this forum like this) to stop this forum from converting the text to links.
UPDATE
OK. I've figured out what the question is (but not the solution)
If you post this with markdown enabled:
Then you expect the Markdown syntax [Link Text](url) to display the text linked to the URL - as apposed to using Markdown to PREVENT URL conversion - which is what I mostly use Markdown for. i.e
AND you don't expect Webex to break the rules based on random positioning of periods, colons and hash characters in the "Link Text" portion.
I think sir (@B Herron), you have found a bug. And another example where MarkDown is not implemented properly in Webex. Like the lack of support for StrikeThrough
