Closed
Bug 56771
Opened 25 years ago
Closed 25 years ago
Warpzilla Tooltips Don't Always Go Away
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: barrymarshall, Assigned: mkaply)
Details
Attachments
(1 file)
Tested with Warpzilla nightly build 1011 on WSeB base with Scitech DD
on TP770X.
You'll probably need a slower machine. Since the code isn't really
optimized yet, I can usually do this on my P2-300 TP, but can't on my
old Aptiva M70 (modified to P1-200 on Win2000).
1) Start Warpzilla.
2) Get a tooltip up.
3) Get Warpzilla busy doing something (loading message, webpage,
whatever).
4) Move the mouse rapidly away from where it was. Avoid places which
could generate tooltips.
You should see a tooltip still present, but the cursor is off the place
for the tip, and it's not connected to the mouse pointer any more.
You can get rid of it by bringing up a new tooltip, but there's
something weird going on in XP for OS/2, since I can't make this happen
under Win32.
The example I have is from MailNews, but I can do it pretty reliably
under the browser as well.
Reporter | ||
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
I see a similar problem under Linux [build 2000101809].
It is similarly difficult to explicitly reproduce, but none-
the-less I see it quite frequently. The "sticky" tooltip also
does not disappear when I minimize the window.
Comment 3•25 years ago
|
||
Reporter | ||
Comment 4•25 years ago
|
||
Probably some sort of XP race condition then, I guess.
Ok, shall we just keep this open for the time being, in case there are
platform-specific patches that have to be put together?
Everyone seems to agree that this is a dupe of 50052. Marking as
such...
*** This bug has been marked as a duplicate of 50052 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 6•25 years ago
|
||
Closing due to dupe. Will track against original problem.
Status: RESOLVED → CLOSED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•