Summary: | www.foo shouldn't be highlighted as link | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Nicolás Alvarez <nalvarez> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | CONFIRMED --- | ||
Severity: | minor | CC: | hein, justin.zobel |
Priority: | NOR | ||
Version: | 1.7.7 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Nicolás Alvarez
2011-08-29 00:29:06 UTC
A change like this would be bad for those that use IRC internally in their organisation and send internal links. ie dev-server.local This bug report is specific to hostnames starting with 'www'. google.com and dev-server.local are already not highlighted as links. Maybe they should be, but that's a separate issue. As long as those aren't linkified, it doesn't make much sense that www.blah is. Internal domains can have subdomains as well so www.somedevserver.local could also be used. Yes, and that works and can continue to work. This is the current state: google.com nothing google.com/search clickable link www.google.com clickable link dev-server.foo nothing test.dev-server.foo nothing www.dev-server.foo clickable link www.foo clickable link <-- this is what this bug is about, I think this shouldn't be a link As I said "two-component domain name that starts in 'www'". Ahh OK my apologies. Confirmed on 1.7.7. |