MySQL Bugs: #49309: Workbench File Import Log disappears if you scroll over it

Bug #49309	Workbench File Import Log disappears if you scroll over it
Submitted:	1 Dec 2009 22:42	Modified:	16 Jun 2010 16:12
Reporter:	Chris Calender	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.10	OS:	Windows (Vista 32-bit)
Assigned to:		CPU Architecture:	Any
Tags:	import log

Description:
The Import Log will disappear if you scroll over the message.

How to repeat:
Import a file using Workbench (i.e., "Import From Disk" tab).

After importing, you will see a message appear in the "Log" section.

If you scroll over this message, the message will disappear.

You then have to minimize and then maximize your screen for the message to re-appear.

Suggested fix:
N/A

Hi Chris

We're not having much luck repeating the problem, can you post a screenshot of the issue?

I've attached the two screenshots.

The first is just after the import completes.  In the lower right-hand side of the page, you can see the "log" entry.

In the second image, you can see the "log" entry has disappeared.  This occurs as soon as I move the mouse anywhere in the "Log" section, for instance, if I attempt to copy/paste the text.

The "log" entry will re-appear if I "minimize" and then "maximize" that window.

However, you are never able to copy/paste the text, as it will always disappear as soon as you get your mouse cursor too close.

It is hard to argue with the screenshots, but without some method to repeat the bug or any kind of clue on what is going on, there isn't much we can do about it; so I set it to Open until someone else can repeat it. But this does seem to be caused by something specific to the reporters system.

Please, check if this is still repeatable for you with WB 5.2.21. If it is, please, send the results from Help > System Info menu item.

I was not able to reproduce this using WB 5.2.21, so consider this fixed.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".