Bug #50281 Result row heights/cell widths wrong sizes when toggling cell wrapping
Submitted: 12 Jan 2010 15:37 Modified: 18 Feb 2010 12:23
Reporter: Alex Whitman Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.16 OSS Beta R5249 OS:Windows
Assigned to: Assigned Account CPU Architecture:Any

[12 Jan 2010 15:37] Alex Whitman 
Description:
Toggling the wrapping of cell contents on a query result tab doesn't reset the height of the row.  If you turn on cell wrapping, the row height will grow if required.  Turning cell wrapping off again doesn't shrink the row height.

How to repeat:
- Create a table with at least one TEXT column
- Insert some dummy text which contains line breaks into the TEXT column, some lorem ipsum will do.
- SELECT the data from the table, a simple SELECT * will work
- Turn on wrapping of cell contents: row heights will increase to accommodate but the width of the TEXT column cells doesn't shrink.
- Turn off wrapping of cell contents: the text will be shown on one line but the row height does not shrink back to the height of one line of text

Suggested fix:
When turning on wrapping of cell contents, shrink the width of the cells.
When turning off wrapping of cell contents, shrink the height of the rows to the height of one line.
[13 Jan 2010 8:07] Valeriy Kravchuk 
Thank you for the problem report. Verified just as desribed.
[18 Feb 2010 12:23] Alex Whitman 
This has returned in 5.2.16 OSS Beta Revision 5249.  In 5.2.15 TEXT fields were shown as blobs so couldn't be word wrapped.  TEXT fields in 5.2.16 are now back showing as text.
[26 Jul 2015 6:00] Paul Weiss 
This is still the case in 6.3.4.0, Windows 7.
[14 Sep 18:01] Omer Barnir 
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.