MySQL Bugs: #104971: Bad UI in Mysql Workbench: the edit area is smaller than the Windows it is in

Bug #104971	Bad UI in Mysql Workbench: the edit area is smaller than the Windows it is in
Submitted:	17 Sep 2021 13:22	Modified:	23 Oct 2021 13:46
Reporter:	Jiafu Gao	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	8.0.26	OS:	Windows (Microsoft Windows 10 Enterprise)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	WBBugReporter

Description:
The SQL edit area, marked by white (instead of the grey background), is much smaller than it should be: the window it is in. 

How to repeat:
1. Open the workbench
2. Open an database
3. Check the mysql editor window - the marked white area
4. COpy/paste a large body of text in it: text is not showing when it pass the left edge of the white area.

Suggested fix:
The white area should be the same size of the window it is in.

Screenshot of bad edit area size

Attachment: editorsizeissue.png (image/png, text), 80.15 KiB.

Update the screenshot to mark the issue

Attachment: editorsizeissue.png (image/png, text), 91.65 KiB.

Hello Jiafu Gao,

Thank you for the bug report.
Imho this is not a bug. Please check the documentation available at https://dev.mysql.com/doc/workbench/en/wb-sql-editor.html
You can adjust the layout by dragging the adjacent sides.

Regards,
Ashwini Patil

There is no way I can adjust the size of the editor area: the mouse don't change into a sizing icon when it moves over the edge of the area. 

Also, I don't see a use case where you want the edit area to be smaller than the window it in - there is no other control than can use the window client area - what's the point leave the blank?

Please reopen.

Hello Jiafu Gao,

Thank you for the feedback.
Try to re-install using the repair option.

Regards,
Ashwini Patil

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".