Version: 0.17 #3011 (using KDE 3.4.1, Debian Package 4:3.4.1-1 (3.1)) Compiler: gcc version 3.3.6 (Debian 1:3.3.6-5) OS: Linux (i686) release 2.6.8-2-686 When there is a lot of whitespace below a line of text containing an URL (which is made into a hyperlink), clicking anywhere in the area directly below the hyperlink causes the Konversation to open that link in a browser. Note that the mouse pointer shape is NOT the same when hovering below the link (normal arrow) as it is when hovering over the link itself (hand/link shape). In the attached screenshot, I've included an example screenshot with an URL towards the top of a mostly empty channel tab, and highlighted the area which seems to be clickable. (i.e., the link itself, and the area directly below it) Thanks!
Created attachment 11797 [details] Screenshot showing where link is clickable, but shouldn't be
Note, I played with it a little more, and discovered that if I double click _below_ the line of text (say, at the very bottom of the screen), and to the right of it (where clicking did not open a new browser), it selected the link. It seems in Qt that clicking, double-clicking and clicking-and-dragging in widgets such as the Konversation channel tabs, or this HTML <textarea> tag in this bug report form, acts as though you're clicking/etc. on the very last line of text. (I'll add two more screenshots to show what I mean.)
Created attachment 11798 [details] HTML <textarea> before double-clicking nowhere near text
Created attachment 11799 [details] HTML <textarea> before double-clicking nowhere near text
Created attachment 11800 [details] HTML <textarea> before double-clicking nowhere near text
Created attachment 11801 [details] <textarea> after double-clicking nowhere near text
Can you test with latest SVN ?
Unfortunately, not at this time. I'm running 3.4.1 out of alioth.debian.org for Debian/etch, and don't have time to do a source-build. Sorry :(
fixed in SVN. Still, the area *above* the link seems to be clickable, too. We can't do much about that, though, so I'm closing this bug for now.