You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a new table is created—whether through copy-pasting, markdown imports, or by loading fresh editor JSON without defined column widths—it often appears poorly formatted by default. Specifically, the column widths are not automatically adjusted to fit the content, leading to tables that are difficult to read and require manual resizing.
For example, in our project, we use markdown as the source of truth, which means we do not store column widths. As a result, every time a document is loaded into the editor, users have to resize table columns repeatedly, which is inefficient and frustrating.
Proposed Solution
To improve the user experience, the editor should automatically calculate and apply column widths based on the table's content whenever no explicit widths are provided.
Screenshots
Current Behavior:
When a table is created without specified column widths, the columns appear misaligned, as shown below:
Desired Behavior:
For comparison, when the same table is pasted into Notion, the column widths are automatically adjusted to fit the content:
The text was updated successfully, but these errors were encountered:
AlessioGr
changed the title
Feature: automatic table column width calculation when new table is created
Feature: Automatically Adjust Table Column Widths Based on Content for New Tables
Dec 31, 2024
This isn't really something in lexical's table implementation, this is the TableCellResizer plugin's doing… which is just a playground plugin and not something that's distributed for re-use. I would recommend modifying your copy of the plugin according to your use case, e.g. disabling the transform that sets the default width on every column and coming up with your own scheme.
Problem Description
When a new table is created—whether through copy-pasting, markdown imports, or by loading fresh editor JSON without defined column widths—it often appears poorly formatted by default. Specifically, the column widths are not automatically adjusted to fit the content, leading to tables that are difficult to read and require manual resizing.
For example, in our project, we use markdown as the source of truth, which means we do not store column widths. As a result, every time a document is loaded into the editor, users have to resize table columns repeatedly, which is inefficient and frustrating.
Proposed Solution
To improve the user experience, the editor should automatically calculate and apply column widths based on the table's content whenever no explicit widths are provided.
Screenshots
Current Behavior:
When a table is created without specified column widths, the columns appear misaligned, as shown below:
Desired Behavior:
For comparison, when the same table is pasted into Notion, the column widths are automatically adjusted to fit the content:
The text was updated successfully, but these errors were encountered: