MySQL Bugs: #76520: Resultset Column & row heights don't adjust to 'ResultSetGrid Font' setting

Bug #76520	Resultset Column & row heights don't adjust to 'ResultSetGrid Font' setting
Submitted:	28 Mar 2015 20:15	Modified:	19 Jan 2017 22:25
Reporter:	Sam Abboushi	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.3 Community, 6.3.7 (1199 build)	OS:	Windows (W1064)
Assigned to:		CPU Architecture:	Any

Description:
I just upgraded to 6.3 and now the Result row heights don't adjust to 'ResultSetGrid Font' setting.

Workaround: Toggle wrapping of cell contents

How to repeat:
Workbench Preferences -> Fonts & Colors -> ResultSet Grid: Arabic Typesetting 32

Perform a query.  Note how row heights are sized to a much smaller font and chopping off half the bottom half of each row's content.

Suggested fix:
Auto-adjust Result row height to accommodate ResultSet Grid defined font size.

Thank you for the bug report. Are you able to attach a screenshot of this issue?. Thanks.

Screen shot of problem with result grid row height

Attachment: Capture.PNG (image/png, text), 46.49 KiB.

Thank you for the screenshot.
Looks like this issue is with other fonts as well with size 32.

Thanks,
Umesh

Resultset Grid Column Headers don't expand to fit font size

Attachment: workbench.JPG (image/jpeg, text), 36.31 KiB.

I just upgraded to 6.3 Community, 6.3.6 (511 build) and this is worse:

Now, Resultset Grid Column Headers don't expand to fit 'ResultSetGrid Font' setting font size making column headers illegible and no workaround I have found.  I have posted a screen shot.

Please advise if I should open this as a new bug.

(Ignore: comment added to correct Synopsis)

Yeah, I'm having this problem as well when I set the result set font to a value higher than 13.

Still same problem with W1064 and 6.3 Community, 6.3.7 (1199 build)

Serious problem when I can't see the column headings!!

Posted by developer:
 
Fixed as of the upcoming Workbench 6.3.9 release, and here's the changelog entry:

When the resultset grid in SQL Editor was set to a font type and size that
exceeded the default row height, the output from a query hid a portion the
row content instead of increasing the row height to accommodate the font
value.

Thank you for the bug report.

Bug is back in version 6.3.9 CE. I installed back the previous 6.3.8 CE and there result set text looks ok even with larger fonts.

Don't know if one would consider this fixed. Upgraded from 6.3.8 > 6.3.9 and row heights are by default, much smaller now

Attachment: mysqlworkbench.jpg (image/jpeg, text), 8.12 KiB.

I agree with Georald Camposano. The text in each row is cut off at the bottom using the default font size (Tahoma 8) in 6.3.9. This means underscores (_) are invisible, letters like 'gjypq' are cut off, commas look like periods, and semicolons look like colons!

Interestingly, if you toggle "Wrap Cell Content" button, the rows are resized correctly.

On the other hand, I guess choosing a larger font size does work (although toggling wrap still changes the height by a couple of pixels...). Should we reopen this or log a new bug?

select 1, 'under_score', 'gjypq', ',.;:' UNION select 2, 'under_score', 'gjypq', ',.;:';

Attachment: mysqlwb_6.3.9_cutoff_text.png (image/png, text), 5.27 KiB.

I am experiencing the same issue where the underscores and tails of characters such as "p", "q", "y", etc. are being cut off.  The line size seems to be set to the same height as the character size without leaving room for the character tails.

The "line wrap" workaround isn't very effective for rows with large text columns, and it doesn't "stick".  It has to be clicked every time.

Very annoying.

Related https://bugs.mysql.com/bug.php?id=84999

This is not fixed.
The descender portion of the letters (e.g., the tail in "Q") is cutting off. This is really frustrating because it makes a "Q" look like an "O"...I spent a chunk of time thinking I had the wrong ID in the database before I realized it was just a display problem in Workbench.

I am using Workbench 6.3.9 build 10690321 CE (64 bits) on Windows 10 Pro, which is the the most up-to-date version as of 5-Oct-2017.

Just wanted to confirm that this is not fixed on the latest as of today (Oct 5 2017).

Workbench 6.3.9 build 10690321 CE (64 bits) on Windows 10 Pro

The Q's looking like O's is annoying for sure, but even worse is that underscores are not visible at all. Lower case y's look like v's, etc.

Just to confirm it is still not fixed with version 6.3.10 12092614CE 64bits, Windows 8.1 Pro

Really sad this bug still exists in 6.3.10

I find hitting the "Toggle wrapping of cell contents" button fixes this. Unfortunately, it must be done each time you get a new resultset.

I cannot fathom why this isn't fixed already. It can't be that hard when clicking the "Wrap Cell Content" button essentially does the same.

You (should) know that when tooling sucks, the *entire* product experience is affected by this? Since I upgraded to whatever version it was that introduced this I hate working with MySQL because PHPMyAdmin sucks balls, period, and now MySQL Workbench sucks balls too... If I had a nickle for every time I missed an underscore or mistook a "p" for an "o" because the descender isn't visible...

https://i.imgur.com/aNfZHf2.png

Case in point...

It seems to be fixed in 8.0.15, at least on Windows 10. It took almost 4 years, which is amazing.