If they are really part of the header then it makes no sense to merge them with the data cells. They are part of different elements so they shouldn't be merged.

I was a bit in doubt on this one. It should be possible to extend the thead.
On the other hand: it's still possible to insert an extra row in thead and copy/paste data from tbody into it if needed.

http://dev.fckeditor.net/ticket/2777

http://dev.fckeditor.net/ticket/2778

http://dev.fckeditor.net/ticket/2656

@kwillems, thanks for the new patches.

We are under beta stabilization now, so I'm afraid those tickets will be retarget to a future release. Only critical tickets should be targeted to the 2.6.4 at this point.

http://dev.fckeditor.net/ticket/2389

http://dev.fckeditor.net/ticket/2487http://dev.fckeditor.net/changeset/2906

I noticed some unwanted results when deleting columns or rows.
Well ... I think it's unwanted.

Say we have a 3 * 2 table like this:

<table title="tabel" cellspacing="0" cellpadding="0" summary="table">
    <thead>
        <tr>
            <th scope="col">1</th>
            <th scope="col">2</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>a</td>
            <td>b</td>
        </tr>
        <tr>
            <td colspan="2">c</td>
        </tr>
    </tbody>
</table>

Now right click in cell b and delete that column.
You will see that the colspan of cell c is not lowered (or, in this case, removed).

To my opinion the best thing to handle those situations is to lower the colspan in cell c.
It could be achieved bij making use of a tablemap when deleting a column.

The same issue appereas when deleting rows with rowspanning cells in it.

Or should it be left the way it's working now?

It would be definitely better to have those code simplifications and fixes when doing those operations. The current behavior doesn't bring that much problems, but it's always good if we can have a cleaner output.

You're great Koen!

http://dev.fckeditor.net/ticket/2800

<table width="200" cellspacing="1" cellpadding="1" border="1">
    <tbody>
        <tr>
            <td>&nbsp;a1</td>
            <td rowspan="2">&nbsp;b1</td>
        </tr>
        <tr>
            <td>&nbsp;a2</td>
        </tr>
    </tbody>
</table>

b1

<table width="200" cellspacing="1" cellpadding="1" border="1">
    <tbody>
        <tr>
            <td>&nbsp;a1</td>
            <td rowspan="2">&nbsp;b1</td>
            <td>&nbsp;</td>
        </tr>
        <tr>
            <td>&nbsp;a2</td>
            <td>&nbsp;</td>
        </tr>
    </tbody>
</table>

<table width="200" cellspacing="1" cellpadding="1" border="1">
    <tbody>
        <tr>
            <td>&nbsp;a1</td>
            <td rowspan="2">&nbsp;b1</td>
            <td rowspan="2">&nbsp;</td>
        </tr>
        <tr>
            <td>&nbsp;a2</td>
        </tr>
    </tbody>
</table>

http://dev.fckeditor.net/ticket/2486

I wouldn't say it's breaking the table layout.
It's more an issue what the user expects.

I can live with it, because now the tablehandler continues the normal way of presenting cells (whereas I consider merged cells to be an exception).

http://dev.fckeditor.net/ticket/2813

http://dev.fckeditor.net/ticket/2800

http://dev.fckeditor.net/ticket/2859

I have a question.
In Gecko one can only merge cells by selecting them all.
In other browsers merging can only be achieved by putting the cursor into one cell and do 'merge right' or 'merge down'.

Wouldn't it be better to enable 'merge right' and 'merge down' in Gecko too?
In that case 'merge right' and 'merge down' are enabled in all browsers and in Gecko 'merge' is enabled too.

http://dev.fckeditor.net/ticket/2868

Thanks for the testing. 
I guess that I might fix them as part of #1865 because I think that it might need a great review of all the code involved.