Testing shows the Link Browser inserting a link into the RTE with the href:

  http://en.wikipedia.org/wiki/Greenspun's_tenth_rule

inserting a link into the RTE with the string:

  <a href="http://en.wikipedia.org/wiki/Greenspun's_tenth_rule">http://en.wikipedia.org/wiki/Greenspun's_tenth_rule</a>

Apostrophes as part of ASCII are permitted in URIs, so this link attribute should be passing through our converters without molestation. Checking the xHtml in the POST to https://extranet.atlassian.com/pages/rendercontent.action, no unexpected escaping seems to be occurring. It might be worthwhile feeding that <a> string into one of our converter unit tests and see what comes out the other side.

Thanks mquail. Great video, note to others: it has sound.
akazatchkov, you probably want to move this to CONF, and I'd bet it's been around since 4.0. I think there's a 40% chance dtaylor will be able to immediately tell you how it's broken.

This issue originally came to my attention because people assumed that Matt has awesome pasted from wikipedia, but he didn't. (If he had he wouldn't have had to stuff around with the dialog at all. Don't know what he was thinking).

same problem exists. I'll make a movie

mquail, I never managed to reproduce this and I wonder whether it was a very temporary problem with whatever SNAPSHOT was on EAC that week. At the time I looked at it as a possible autoconvert bug, but I really don't think it was. Does the link still not edit? (I don't have permission to edit the comment)

pong

Don, no the issue you're referring to was a support case that mseager was looking at that turned out to be pretty unrelated to this bug report (the customer's problem was that all links were getting converted to plain-text paragraphs on save). It was just a wild stab in the dark that this issue could be related; in hindsight, I doubt that it is.

Hi Joe,
I think you told me you encountered something like this on 4.0. Was it the same?

Weird. I guess the next step is for us to look at what awesome state the XML has got into, and then figure out how, and why it's so bad.

I originally created the comment in chrome (stable). I added the link with cmd-k then pasted in the link into the textbox.

I then tried over and over again to edit the comment in chrome and safari. If I put the cursor into the link, I got the edit/unlink hoverbuttons, which brought up the dialog with the correct values.

I added a comment to another blog post later that day, and links in that one seemed to work fine.

I don't have speakeasy activated