Bug #50217 UI: System Profile fields slide out of view on resize
Submitted: 10 Jan 2010 21:24 Modified: 11 Jan 2010 11:26
Reporter: Chris Bednarski Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.11 OSS Beta 4842 OS:Windows (XP Pro x64)
Assigned to: CPU Architecture:Any
Tags: configuration file, manage server instances, server administration, system profile, windows xp, workbench

[10 Jan 2010 21:24] Chris Bednarski
Description:
This is a user-interface problem.

Two of the System Profile fields in the server management window, named "Path to configuration file:" and "Section [name] from configuration file:" are initially positioned such that they spill off right right side of the window.

Furthermore, when the window is resized from any side and in any direction, both fields slide to the right, resulting in them eventually disappearing off of the right side of the window.

How to repeat:
From the Home screen:

1. Click [Manage Server Instances], under the [Server Administration] heading
2. Create [New] or select extant [Server Instance]
3. Select [Connection] on [Connection Tab] so [System Profile] tab is activated
4. Switch to [System Profile] tab
5. Resize the top or bottom edge of the window, noting the position of the configuration file fields.

Suggested fix:
These fields should be properly positioned (so that they are visible) when the window is first opened.  Also, the fields should expand to fill the window as it is resized, rather than moving as it is resized.
[10 Jan 2010 21:26] Chris Bednarski
Screenshot of window with fields sliding away

Attachment: sliding_fields.png (image/png, text), 18.22 KiB.

[10 Jan 2010 21:31] Chris Bednarski
It appears that in addition to the two fields noted sliding away, the right side of all other fields in the System Profile tab also slide away.  Because they are anchored on the left, you can still see them, but their right ends disappear.
[11 Jan 2010 11:26] Johannes Taxacher
it's not obvious, but it's actually a duplicate of Bug #48222 which has been fixed in the meantime. the fix for that will be included in upcoming version 5.2.12