I imagine this has been discussed a bunch before, but my searching wasn’t able to find relevant threads.
I’d like to discuss whether whitespace (literally just the space character on standard keyboards) can be allowed in link URLs?
My use case is the markdown of my README on my github repo, where I had links to content in directories where the directory names had spaces. Github has always allowed this, and then when they switched to cmark, it broke my links. That is, they don’t parse as links at all, and just show up as text in the page, which is awful.
My problem with manual encoding of spaces as
%20 is that on more than a few occasions I’ve fat fingered it as
%29 and didn’t catch the problem until much later when the links were broken but not obviously so unless you actually tried to click on them. Hitting space is much more natural, which it seems to me fits with the general mindset of what Markdown tries to make easy for authors.
<a href="http://some.tld/link with spaces/">foo</a> into my markup seems to still work just fine, so it’s really unfortunate that
[foo](http://some.tld/link with spaces/) is now broken.
Browsers definitely still work with URLs where the space isn’t encoded, and some even still display without the encoding, like Firefox:
I’m aware it’s a long shot at this point, but I’m just curious if it’s possible to reconsider and relax this restriction? And if not, I’d appreciate more info on why not. Especially, I’d like to understand how Github was able to get away with allowing this for many years and it didn’t seem to ostensibly break anything?