240388 - Losing cell-join and cells when deleting a column/collum/colom

Status: RESOLVED EXPIRED

(Core :: DOM: Editor, defect)

Description

[Gerke Kok]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040406
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040406

When one deletes a column in a table and there are cells in the next column that
are joined, this join is dropped and new cells are inserted.

Reproducible: Always
Steps to Reproduce:
1. Create a table of 7 rows/5 cols
2. Join cells (4,2) until (4,3). (for the result see:
http://kok.thuis99.org/testoo/test_col_delete.html)
3. Delete col 3.
4. The whole layout is messed up as one can see on page
http://kok.thuis99.org/testoo/test_col_delete_fail.html

Actual Results:  
The restult can be seen on page:
http://kok.thuis99.org/testoo/test_col_delete_fail.html

Expected Results:  
I would like only column 3 to be removed. And I would like to see this as the
result:
   http://kok.thuis99.org/testoo/test_col_delete_ok.html

Comment 1

[Gerke Kok]

One also loses some cells that should not have been deleted.

Comment 2

[Gerke Kok]

Attachment: The original table

Comment 3

[Gerke Kok]

Attachment: The table where the wrong cell have been deleted

Comment 4

[Gerke Kok]

Attachment: The table with the correct cells deleted

(done manually so we know what is going on)

Comment 5

[chris hofmann]

do you know of if this is a regression, or when the problem was introduced? 
down to trying to fix critical regressions for 1.7

Comment 6

[chris hofmann]

cc bernd in case this has impact in table code...

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This sounds relatively obscure, doesn't sound like a regression, and doesn't
seem likely to be fixed for 1.7.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.