Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Vaguely related to:
Links to URLs containing parentheses

This is likely to do with encoding URLs for safety, but here's a case that works in the preview and the rollover title is "Speakers" yet breaks when posted:

[Boston Dev Days][1]


The outcome looks like this: Boston Dev Days

While the preview looks like this: Boston Dev Days

If you haven't yet spotted the difference, please mouse over each link above.

It is proper to put a space between the url and the parenthesis, but the preview accepts the improper format.
I might note this is a preview bug.
The preview will lead you to think that the format shown is a correct way of adding a comment/title to a url. It is not.

Also breaks if you use [multiple words][4] yet shows in the preview fine. And lastly, if you make a code block like the one I just made, then use control-L to link a word later on, the url number for [1] which should have been the "outcome" line, becomes [2] and [1] remains assigned as it was, but is mistakenly assigned to the non-linked text in the code block.

Clearly these are minor, but it's worth noting for completeness.

[4]: words)

share|improve this question
I always give my links names [Perl::Module]: – Brad Gilbert Aug 27 '09 at 22:11
Dupe…, additionally, spaces are not valid URL characters – Ian Elliott Aug 27 '09 at 22:12
yeah, when you look at the PREVIEW the (multiple words) are not parsed as part of the URL. You are misled to believe that the format host/path(comment) is acceptable. It is not. So the preview is wrong. Simple? – dlamblin Aug 28 '09 at 17:31

Probably that feature ( or bug ) was introduced around the time Jeff wrote this:

The Problem With URLs

share|improve this answer

The title issues are fixed now (or will be after the next deployment). The URL numbering bug I cannot reproduce; considering that this bug report is almost 1 1/2 years old, this has probably been fixed since then.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .