Bug #81756 Action Output in MySQL Workbench does not scroll to end automatically
Submitted: 7 Jun 2016 16:25 Modified: 10 Jun 2016 4:03
Reporter: Daniel Rice Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.5.0 (build 397) OS:MacOS (10.11.4)
Assigned to: CPU Architecture:Any

[7 Jun 2016 16:25] Daniel Rice
Description:
When executing queries in MySQL Workbench, the Action Output will not automatically scroll to the end. It will, instead, scroll to the last selected line in the output. This is not the behavior I've observed in the Windows version of MySQL Workbench and it's quite annoying to have to click down to that window and scroll to the bottom after executing a query.

How to repeat:
Execute many queries so that the Action Output is full. Continue executing queries and observe that the output does not change. Scroll down and see the new output. 

Suggested fix:
Have the Action Output window automatically scroll to the bottom on query execution.
[9 Jun 2016 9:16] MySQL Verification Team
Hello Daniel Rice,

Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.

Thanks,
Umesh
[9 Jun 2016 17:04] Daniel Rice
I upgraded to 6.3.6 and the issue is fixed. There may have also been an issue with the check for upgrades because

Help-> Check for updates 

showed that I had the latest version.
[10 Jun 2016 4:03] MySQL Verification Team
Thank you Daniel Rice for confirming that you are not seeing the issue after upgrade to 6.3.6.
Coming to the other issue which you observed i.e Check for updates does not find newer version is also fixed in 6.3.6 with Bug #75132

Closing the bug for now.

Thanks,
Umesh