Opened 16 years ago
Closed 13 years ago
#2656 closed Bug (invalid)
Table: insert row/column produces unexpected results in the presence of merged cells
Reported by: | thiloplanz | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Core : Tables | Version: | FCKeditor 2.6.3 |
Keywords: | Cc: |
Description
In the presence of merged table cells (colspan or rowspan), inserting rows or columns produces table rows with missing cells.
(see the attached picture, where the cell in the lower right corner is missing)
The user would expect the merged cells to be extended (increasing the colspan or rowspan), for example like Excel or TinyMCE do it, or at least end up with an appropriate number of unmerged cells.
Attachments (2)
Change History (9)
Changed 16 years ago by
Attachment: | DocumentLocalFile.jpg added |
---|
comment:1 Changed 16 years ago by
comment:3 Changed 16 years ago by
Keywords: | Confirmed added; table colspan rowspan removed |
---|
Confirmed the problem in both IE and FF.
Changed 16 years ago by
Attachment: | 2656.patch added |
---|
comment:5 Changed 16 years ago by
In tablehandler.js currently a clone is made of the row or column to copy it. Problems occur when those rows have cells spanning rows or columns.
I made a patch to insert just flat rows or columns (without colspans or rowspans). Furthermore I disabled the possibility to insert new rows or columns in certain occasions. For example: in the above picture I disabled the ability to insert a new row before/above cell a, since that cell is rowspanned by the cell in the preceding column.
So one has to insert new rows or columns at logical places in the table.
comment:6 Changed 14 years ago by
Component: | General → Core : Tables |
---|
comment:7 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | confirmed → closed |
FCKeditor was retired and is no longer supported. All active development was moved to its successor, CKEditor 3.x, that is a fully mature and far superior product. We recommend you upgrade as soon as possible since this issue is no longer a problem in current code base.
This issue is no longer valid
screenshot