-
Notifications
You must be signed in to change notification settings - Fork 8
Escape HTML in urls #5
Comments
Turns out It's kind of a shame, since I think users expect the escaping to Just Work(tm). I actually filed this because I saw a user mispaste a URL and they were surprised when it rendered useless useless HTML. @Flet: what do you think about closing this as Working As Intended? I've filed something against Friends on the subject, since IMHO pasting images into a channel shouldn't require this much deep knowledge of the commonmark spec. |
Yep |
What do you think about the suggestion in moose-team/friends#105 to mimic Slack in that we inline image URLs directly? Seems like a pretty lightweight addition to |
@noffle just posted there :) moose-team/friends#105 (comment) I think it makes sense as long as users can turn it off. I also think we should go for more permissive URL parsing in markdown. |
On a mini crusade here. The current Markdown Spec doesn’t explicitly prohibit spaces in image links, but indirectly prohibits them in the Links section, where it says spaces cannot be used either with or without I say the spec is vague on this, but that it seems they do intentionally wish to prohibit spaces, even escaped. |
From @noffle on April 30, 2015 17:33
As is, entering something like the following, which was posted into #friends:
![Sorry guys](http://my.setale.me/image/052u2w2q3u3w/Schermata 2015-04-30 alle 19.09.21.png)
will fail because spaces aren't being translated into
%20
s.Copied from original issue: moose-team/friends#86
The text was updated successfully, but these errors were encountered: