Issue Summary

During legacy-to-Cloud editor conversion in migration, tables containing merged cells (rowspan and colspan) without an explicit <colgroup> may have their column structure altered, resulting in misaligned headers and additional empty cells.

The converter incorrectly calculates the column count from the narrowest row without accounting for cells spanning multiple rows.

Steps to Reproduce

1. Open a legacy-editor page containing a table with merged cells (rowspan and colspan) but no explicit <colgroup>.
2. Verify that the table displays correctly in legacy View mode.
3. Click Edit to trigger conversion to the Cloud editor.
4. Observe that the table headers and columns become misaligned.
5. Publish the page and observe that the incorrect structure persists.

Expected Results

The converter should preserve the original table structure, merged cells, and column alignment without introducing additional cells.

Actual Results

• The converter incorrectly calculates the number of columns.
• Existing colspan values may be reduced.
• Additional empty header cells are introduced.
• Headers become misaligned with their corresponding data.
• Publishing persists the incorrect structure.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.