Without the full stop it works fine:
[//foo.org/bar#baz bang]
->
<p><a href="//foo.org/bar#baz">bang</a></p>
… but:
[//foo.org/bar#baz. bang]
->
<p>[//foo.org/bar#baz. bang]</p>
Version: unspecified
Severity: normal
Without the full stop it works fine:
[//foo.org/bar#baz bang]
->
<p><a href="//foo.org/bar#baz">bang</a></p>
… but:
[//foo.org/bar#baz. bang]
->
<p>[//foo.org/bar#baz. bang]</p>
Version: unspecified
Severity: normal
Also:
[//foo.org/bar bang]
->
<p><a href="//foo.org/bar">bang</a></p>
… but:
[//foo.org/bar. bang]
->
<p>[//foo.org/bar. bang]</p>
The tokenizer parses the link fine, but the LinkHandler seems to think it's invalid & converts it back to text.
The issue is that the url production in the tokenizer is used both for urllinks and the validation of general links via tokenizeURL. URL links are supposed to avoid eating trailing commas, colons and stops. In other hrefs those are fine though.
We should probably split the urllink production from the more general url production.
Change 126853 had a related patch set uploaded by Cscott:
WIP: Fix a number of link-parsing and serialization issues.
Change 126853 merged by jenkins-bot:
Fix a number of link-parsing and serialization issues.