Bug 84676

Summary: long URLs part-scrolled out of the screen cause miscomputation of location of other URL
Product: [Retired] Red Hat Linux Reporter: Alexandre Oliva <aoliva>
Component: xchatAssignee: Mike A. Harris <mharris>
Status: CLOSED RAWHIDE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-20 16:51:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot with the mouse cursor over the second url (underline not present because Alt-PrintScreen removes it)
none
same portion of the window, after moving the mouse over the first url none

Description Alexandre Oliva 2003-02-20 07:33:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206

Description of problem:
If there are two multi-line URLs next to the beginning of an xchat panel, such
that at least one line of the first URL has scrolled out of the panel already,
if you position the mouse over the second URL, such that it is underlined, let
it rest for one second, then move it over the appearing part of the first URL,
you'll see the second URL  be displayed some lines down to its current location.
 The number of lines is given by the number of lines in the first URL that have
already scrolled out of the screen.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1.Open xchat, connect to some server, and start a dialogue with yourself (just
so that you can more easily duplicate the problem)
2.enter a very long URL (enough to take up 2-4 lines of the display).  you'll
get the URL back from the server, which is handy because we need two of those,
one right after the other
3.send yourself short (one-line) messages until part of the first URL scrolls
out (if it scrolls entirely out of the screen, using the scroll bar to move back
doesn't help, I couldn't duplicate the problem in this case)
4.move the mouse over the second URL (the one that appears entirely), and let it
rest for a second or so
5.move the mouse over the part of the first URL that is still displayed

Actual Results:  Most times, you'll see your nick appear on the left on a line
it wasn't before, and some garbage will likely overlap with part of the URL, and
a few more lines down.  After some investigation, you'll note that it is exactly
the message of the second URL that, instead of being re-displayed in its current
location to clear the underline from the active URL, was displayed a few lines
too low, with the number of lines corresponding to the number of obscured lines
in the first URL.  The same number of lines in the second URL remains underlined
(since the very image that was supposed to clear the underlines was displayed in
the wrong location).

Expected Results:  It should clear the underline by displaying it on the correct
position.

Additional info:

Scrolling up and down removes the garbage.

Comment 1 Alexandre Oliva 2003-02-20 07:41:55 UTC
Created attachment 90208 [details]
screenshot with the mouse cursor over the second url (underline not present because Alt-PrintScreen removes it)

Comment 2 Alexandre Oliva 2003-02-20 07:42:56 UTC
Created attachment 90209 [details]
same portion of the window, after moving the mouse over the first url

Comment 3 Mike A. Harris 2003-02-21 14:16:08 UTC
Wow!  That's pretty thorough!  ;o)

Not mission critical right now though, but I'll try to reproduce sometime
and have a gander.

Comment 4 Mike A. Harris 2003-05-18 01:32:06 UTC
I just built xchat 2.0.2-1 in rawhide.  Can you please test it on RHL 9, and
see if this problem goes away for you?  If so we can close it, if not, time
to debug.  ;o)

Comment 5 Alexandre Oliva 2003-06-20 16:51:01 UTC
Sorry abou the long delay in testing this.  I've just upgraded a box to
xchat-2.0.2-8, and the problem is indeed gone.  Thanks!