TYPO3 Core

What configuration do you have in TS setup for lib.parseFunc_RTE ?

Shyly I reply with...

1. === Output parsing ===
   lib.stdheader >
   lib.parseFunc.nonTypoTagStdWrap >
   lib.parseFunc.tags.link.typolink.target >
   lib.parseFunc.allowTags = table, tbody, tr, th, td, col, h1, h2, h3, h4, h5, h6, div, p, br, font, span, ul, ol, li, pre, blockquote, strong, em, b, i, u, sub, sup, strike, a, link, img, nobr, hr, tt, q, cite, abbr, acronym, address, object, embed, param, map, area
   lib.parseFunc_RTE >
   lib.parseFunc_RTE < lib.parseFunc

Remove the last two lines and the thead element will be rendered correctly.

I had the same problem,
found the following option:

RTE.default.proc.entryHTMLparser_db.tags {
thead.allowedAttribs = class, style
tfoot.allowedAttribs = class, style
}

...and thead is rendered correctly!

@Iomedia: I don't think so. This is a FE-rendering configuration issue. You must have changed something else.

It may sound silly to you,
I didn't change anything else except this lines and it rendered correctly.

I would be glad if there would be a more logical solution.

Maybe you can test it yourself ?
Or someone else maybe ?

I can reproduce this issue only by using the TS setup reported by Matthew.

Using the default proc options and default lib.parseFunc_RTE, the issue does not arise.

At last I found the error:

I had to allow <thead> explicitly in "allowTags ="
Fine, now it is working correctly.
Thanks for your answers.

btw, I tried to set "allowTags = * ",

it doesn't work as in "showButtons = * " ???

thead is included in the default configuration
RTE.default.proc.allowTags and
RTE.default.proc.entryHTMLparser_db.allowTags

If you need to modify these lists, I would recommend that you do it by difference with
RTE.default.proc.allowTags := addToList(tagName) or
RTE.default.proc.allowTags := removeFromList(tagName)

and

RTE.default.proc.entryHTMLparser_db.allowTags := addToList(tagName) or
RTE.default.proc.entryHTMLparser_db.allowTags := removeFromList(tagName)

I understand now, thanks a lot!

There isn't any bug here, only mis-configurations.

I am therefore closing the issue.