MySQL Bugs: #84999: Resultset Row Height don't adjust to 'ResultSetGrid Font' setting

Bug #84999	Resultset Row Height don't adjust to 'ResultSetGrid Font' setting
Submitted:	14 Feb 2017 17:34	Modified:	16 Feb 2017 9:29
Reporter:	Louis Castorena	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.3.9	OS:	Windows (Microsoft Windows 10 Pro)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
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

How to repeat:
Run query to populate result grid

Thank you for the bug report. Please provide a screen-shot of the font set and the row height issue. Thanks.

MySQL Workbench 6.3.9 Result Grid

Attachment: mysql_workbench_6_3_9_result_grid.JPG (image/jpeg, text), 93.23 KiB.

Thank you for the feedback.

I'm also having this problem with version 6.3.9 and it doesn't matter what font or font size I select, any letter than hangs down like y or p get cropped so y's look like v's.

If I click on the "Wrap Cell Content" the cropping is fixed, but the rows may become huge depending on the row content.

This affects result rows with Chinese too.

Same issue here using MySQL Workbench 6.3.9 with Windows 7 Enterprise edition.

Letter descenders hidden, underscores hidden due to row height

Attachment: MySQLWorkbench_6.3_row_height.png (image/png, text), 2.85 KiB.

The same problem. Workbench version 6.3.9. Is there any solution?

https://bugs.mysql.com/bug.php?id=86543 marked as duplicate of this one.

This issue has been bugging me for some time: Having MySQL Workbench cut off the descenders of lower-case characters (and upper-case Q looking like O).  It really can cause problems in recognizing the data values, leading to errors.

I found a work-around.  I really, really, really want this bug to be fixed, so I hesitate to even post the work-around.  On the other hand, the bug has been there for a while now, and I haven't seen any indication that it is viewed as something important to fix.  (Which it is!)

But in the interim, I don't want to leave others facing the same problems I did.

So here's the work-around: just click the "Wrap Cell Content" icon (right-most icon at the top of the grid area).

Nothing yet ? How hard is this ?

Bug #87963 marked as duplicate of this one

6.3.10 on Windows 10. Bug confirmed. I can't believe this is still an issue after it was apparently fixed in previous versions. I would downgrade but something about SSL capabilities disallows that. I really hope this issue is addressed SOON.

Just downloaded MySQL Workbench 6.3.10 for use on Windows 10 (Home). This bug is present using straight out of the box settings.
This is surely easy to fix? please set the row height in the results grid to be enough to show the full height (including the descenders on letters like "y" and "p") of the Font. Particularly the underscore character is hidden entirely.

Steps to reproduce:-

select 'xp_yvx';

in the result pane you'll notice the "y" and "v" look identical because the descender on the y is obscured, the descender on the p is also obscured and the underscore looks like a space because it too is obscured.

Please Fix.

"So here's the work-around: just click the "Wrap Cell Content" icon (right-most icon at the top of the grid area)."

This works fine until you have some long string of data that contains line breaks. Then the grid height adjusts to the height of the content and makes the table unreadable in that way.

Really hoping this gets fixed soon.

Still an issue for me in v8.0.11 RC, I'm using Windows 10.

I hope that this can be resolved, it cuts off characters such as underscore (which I use a lot for storing codes) making it appear to be a space character...

underscore disappearing

Attachment: 2018 05 24 - 09 39 11 - 1527147552 Image 001.png (image/png, text), 7.85 KiB.

This bug has been reported almost 3 years ago! (https://bugs.mysql.com/bug.php?id=76520)

When will it be fixed?

Still an issue with 8.0.11 on Win 10. Is there any workaround? Is there bug report for 8? Needs a fix or at least some workaround. Changing font or its size does not solve it.

It seems to be fixed in version 8.0.15, at least on Windows 10.