Bug 250321

Summary: choqok 0.9.90 some URL not clickable
Product: [Applications] choqok Reporter: Daniel Eckl <daniel.eckl>
Component: generalAssignee: Mehrdad Momeny <mehrdad.momeny>
Status: RESOLVED FIXED    
Severity: normal CC: gatoso, gmlastik, kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Daniel Eckl 2010-09-06 00:04:33 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

Some URLs are not being recognized and so they are not clickable. Examples include

http://blip.fm/~vsow2
http://j.mp/98EmPR

A search quickly shows that simply all URLs from blip.fm and j.mp are affected. I guess there are more domains affected, if you want, I will add them here as soon as I find more.

Using choqok 0.9.90 on KDE 4.5.1. Sorry, but I was not able to select these values in the ticket.

Reproducible: Always

Steps to Reproduce:
Start a user defined search for "blip.fm" or "j.mp". Look for the URLs.

Actual Results:  
URLs are not clickable.

Expected Results:  
URLs should be blue and underlined and clickable
Comment 1 Andrey Esin 2010-09-07 20:48:41 UTC 

*** This bug has been marked as a duplicate of bug 250408 ***
Comment 2 Daniel Eckl 2010-09-07 20:53:16 UTC 
Hmmm just a question, no offense meant: why's the newer bug not a duplicate of mine instead? I took the time and searched all open bugs before I created mine, the newer bug reporter obviously didn't.

Not that it makes any difference as long as it's fixed, but I'm just curious how things are handled.
Comment 3 Andrey Esin 2010-09-07 20:58:42 UTC 
*** Bug 250408 has been marked as a duplicate of this bug. ***
Comment 4 Andrey Esin 2010-09-07 21:01:21 UTC 
Sorry ;)
Yes, your bugreport was more early.
Comment 5 Daniel Eckl 2010-09-11 22:28:10 UTC 
Today I pulled latest git snapshot and so far I did not find a tweet with unrecognized link. Thank you!
Comment 6 Andrey Esin 2010-09-18 09:50:30 UTC 
*** Bug 251140 has been marked as a duplicate of this bug. ***