13

I noticed something when this question was closed as a duplicate of this one:

Is it valid to replace http:// with // in a <script src=“…”>?

The "possible duplicate" message stripped the http:// from the title like this:

Possible Duplicate:
Is it valid to replace with // in a <script src=“…”>?

It's not hidden or anything, it's just not there:

Is it valid to replace with // in a &lt;script src=&ldquo;&hellip;&rdquo;&gt;?

I always thought it seemed weird that the "possible duplicate" text is inserted into the actual post body instead of something more like the "Linked" section, but that's a different concern altogether I suppose.

Seems low-priority, but could be a sign of other potential issues and seemed unintentional, so I figured I'd report it as I didn't see any mention of it.

3

This was indeed the quickfix for the issue that Shog9 found. Back then, the Markdown converter had link-within-link issues, where

[the http://somewhere thing](http://en.wikipedia.org/wiki/Relevant_article)

would be converted to

<a href="http://en.wikipedia.org/wiki/Relevant_article">the http://somewhere thing</a>

and then the autolinker would kick in, doing this:

<a href="...">the <a http://somewhere">somewhere</a></a>

which is all kinds of wrong.

I did however fix that issue a long time ago, so this workaround isn't necessary anymore. It's removed in the next build.

1

This probably is intentional - since proper URLs are actually converted into links when they appear in post body text, a title with a URL in it would suddenly be a link when inserted into the duplicate box.

Stripping off the http:// is a pretty easy work-around. Except in this case, there's nothing after it...

You must log in to answer this question.