Adium uses rich text. The person on the other end gets it in the form

    example.com/foo (http://example.com/foo)

It's a bug in Chromium, but also an annoying idiosyncrasy of Adium.

PS: Sorry, I accidentally downvoted you.

Check if your behaviour matches one of these:

code.google.com/p/chromium/issues/list?q=label:HTTPStripping

and file a new one if not.

EDIT: I am intentionally not including the "http:// since:

* after looking at it in the omnibox, I decide I like it better this way indeed, and 6 less keystrokes. The others will have to copypaste or the webapp writers will have to figure a way to highlight it :-)

* the copypaste is not working in the linux case either, but that's one of the logged bugs.

It's really the first point that I am trying to say is the biggest impact that this change will have. "If it works in Chrome, it has to work everywhere".

> EDIT: I am intentionally not including the "http:// since:

And I am intentionally not clicking the link because ... it's not a link. I have a greasemonkey script that automatically turns plain text URLs into clickable links. But the text in your post is not a URL. It's a domain and a path, but with no scheme it is not a URL.

Adium's text entry is rich text, it'll accept actual hyperlinks. Paste a URL from Chrome in and right click > 'Edit Link', it should show the correct URL, with the link text as the URL minus http://.