URL's with trailing slashes are not recognized
See original GitHub issueDescription
Mark Text does not always make URL’s clickable when the URL has a trailing slash.
Steps to reproduce
- Open an empty document in Mark Text
- Paste (or type) the following text:
# Link testing
https://www.google.com/
https://www.google.com
https://www.google.com/
Expected behavior:
All three links should be recognized by Mark Text as URL’s and be clickable.
Actual behavior:
Only the 2nd link is clickable.
Versions
- Mark Text: 0.16.1
- Operating system: W10
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Trailing Slashes on URLs: Contentious or Settled?
Performance: when you leave off a trailing slash and the platform expects one (or vice versa), you get a redirect which is a...
Read more >Django trailing slashes in urls are not working correctly - Reddit
I just ran a couple of tests, and with a trailing slash in the urlconf I get the desired behaviour for reverse() regardless...
Read more >Django trailing slashes in urls are not working correctly
In manual check I discovered that initially instead of slash at the end of url browser doesn't see it and redirects to url...
Read more >Trailing Slash Redirect Not Working - WordPress.org
The trailing slash redirect used by my plugin is based on PHP function. Therefore, when PHP cache is enabled, Permalink Manager is not...
Read more >To slash or not to slash | Google Search Central Blog
Choose one URL as the preferred version. If your site has a directory structure, it's more conventional to use a trailing slash with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I am willing to solve this issue.
Yes, @eagleofnorth. You can avoid the problem by writing this:
[https://google.com](https://google.com/)
.