[GH-ISSUE #7767] [Bug] Creating a new item in a select field collapses manually resized columns in a Grid #3424

New issue

Closed

opened 2026-03-23 21:30:03 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 21:30:03 +00:00

Owner

Originally created by @rockerest on GitHub (Apr 17, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7767

Bug Description

When filling out a Grid with a select column, if any column has been manually resized, creating a new item in the select field shrinks all manually sized columns to their minimum size.

How to Reproduce

Create a Grid with three columns like: Text, Select, Text
Resize Column 1 to be very wide
Type in a new value in Column 2, and choose the "Create [...]" option
[optional] Resize Column 3 to be very wide
[optional] Type a new value in Column 2, and choose the "Create [...]" option

Expected Behavior

Resized columns should not shrink to a default size under almost any circumstances.

Operating System

Windows

AppFlowy Version(s)

0.8.8

Screenshots

https://github.com/user-attachments/assets/d3265b72-1347-400f-ae30-2c076440130f

Additional Context

No response

Originally created by @rockerest on GitHub (Apr 17, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7767 ### Bug Description When filling out a Grid with a select column, if any column has been manually resized, creating a new item in the select field shrinks all manually sized columns to their minimum size. ### How to Reproduce 1. Create a Grid with three columns like: Text, Select, Text 2. Resize Column 1 to be very wide 3. Type in a new value in Column 2, and choose the "Create [...]" option 4. [optional] Resize Column 3 to be very wide 5. [optional] Type a new value in Column 2, and choose the "Create [...]" option ### Expected Behavior Resized columns should not shrink to a default size under almost any circumstances. ### Operating System Windows ### AppFlowy Version(s) 0.8.8 ### Screenshots https://github.com/user-attachments/assets/d3265b72-1347-400f-ae30-2c076440130f ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:30:03 +00:00

mirror commented

2026-03-23 21:30:03 +00:00

Author

Owner

@rockerest commented on GitHub (Apr 17, 2025):

After experiencing this more, I think the title is slightly too specific.

If you change a column size at all, it seems like you need to leave the document that holds the Grid and then re-enter the Grid view to "save" the column sizes.

If you adjust a column in any way and then - without leaving - use the "Create [...]" option in a Multi/Select, all the columns will reset back to their "last saved" size. For new Grids, that acts like I described above: the columns all reset to their default smallest size.
However, for Grids that have already been edited and "saved" (by exiting the view and then coming back), the columns may expand, shrink, or not change at all - it just depends what manual user actions have taken place since the last "save."

@rockerest commented on GitHub (Apr 17, 2025): After experiencing this more, I think the title is slightly too specific. If you change a column size at all, it seems like you need to leave the document that holds the Grid and then re-enter the Grid view to "save" the column sizes. If you adjust a column in any way and then - without leaving - use the "Create [...]" option in a Multi/Select, all the columns will reset back to their "last saved" size. For new Grids, that acts like I described above: the columns all reset to their default smallest size. However, for Grids that have already been edited and "saved" (by exiting the view and then coming back), the columns may expand, shrink, or not change at all - it just depends what manual user actions have taken place since the last "save."

mirror commented

2026-03-23 21:30:04 +00:00

Author

Owner

@richardshiue commented on GitHub (Apr 17, 2025):

Hi there @rockerest, thanks for raising this issue. We are going to be releasing a new version soon which will fix this issue. Stayed tuned and do let us know how it goes after you test our new version!

@richardshiue commented on GitHub (Apr 17, 2025): Hi there @rockerest, thanks for raising this issue. We are going to be releasing a new version soon which will fix this issue. Stayed tuned and do let us know how it goes after you test our new version!

mirror commented

2026-03-23 21:30:04 +00:00

Author

Owner

@rockerest commented on GitHub (Apr 17, 2025):

Nice! This seems to be fixed in my brief testing! Nice work!

@rockerest commented on GitHub (Apr 17, 2025): Nice! This seems to be fixed in my brief testing! Nice work!

mirror referenced this issue

2026-03-23 22:20:01 +00:00

[PR #3424] [MERGED] fix: visual bug on board accessory #5723