Summary: | Clickable area of a hyperlink can extend to the bottom of the chat area | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | William Kendrick <nbs> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot showing where link is clickable, but shouldn't be
HTML <textarea> before double-clicking nowhere near text HTML <textarea> before double-clicking nowhere near text HTML <textarea> before double-clicking nowhere near text <textarea> after double-clicking nowhere near text |
Description
William Kendrick
2005-07-14 09:34:55 UTC
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. |