You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When auto_link=True, or when self-linking a URL like "$":http://www.example.com/ the scheme (http://) is removed from the displayed link.
I realize this follows the PHP version, but looking at the history behind that change (textile/php-textile#48 (comment)) it looks like something tossed in without much discussion. I (and several people I showed this to) feel like this was a bad decision, as it makes it less clear that the given text is actually a URL. It seems like there should at least be an option to turn this off.
Ironically, the one case where I think it should be removed is for mailto: links, but it's not. (This does deviate from the PHP version, which removes them.)
The text was updated successfully, but these errors were encountered:
I see your point about stripping the scheme from the URL being unclear. However, I'm trying to match the functionality of the php version as much as possible. There are some issues with how it handles links. Hopefully it will contribute to cleaner code for us.
I've resolved the issue with mailto: links displaying incorrectly. It will be merged in soon-ish.
When
auto_link=True
, or when self-linking a URL like"$":http://www.example.com/
the scheme (http://
) is removed from the displayed link.I realize this follows the PHP version, but looking at the history behind that change (textile/php-textile#48 (comment)) it looks like something tossed in without much discussion. I (and several people I showed this to) feel like this was a bad decision, as it makes it less clear that the given text is actually a URL. It seems like there should at least be an option to turn this off.
Ironically, the one case where I think it should be removed is for
mailto:
links, but it's not. (This does deviate from the PHP version, which removes them.)The text was updated successfully, but these errors were encountered: