[css-tables] Tables Fixup to-be-caused by replaced elements ignored in some browsers

[FremyCompany]

https://drafts.csswg.org/css-tables-3/#fixupAlgo --- step 3.1:

An anonymous table or inline-table box must be generated around each sequence of consecutive proper table child box which are misparented. If the box’s parent is an inline box, then an inline-table box must be generated; otherwise it must be a table box.

A table-column box is misparented if its parent is neither a table-column-group box nor a table-root box.

This is what Edge does in the following example, but not what (most?) other browsers do:

https://jsfiddle.net/5cxwaopc/

I also see that all browsers seems to ignore display:table-column on the input, which is in direct contradiction with what CSS 2.2 stated (I removed the text from css-tables-3 because this clarification was not required as it is the normal expected behavior)

Replaced elements with these 'display' values are treated as their given display types during layout. For example, an image that is set to 'display: table-cell' will fill the available cell space, and its dimensions might contribute towards the table sizing algorithms, as with an ordinary cell.

Elements with 'display' set to 'table-column' or 'table-column-group' are not rendered (exactly as if they had 'display: none'.

What do we want to resolve this issue to? Here are two options:

• (1) Browsers should fix the bugs. No changes to the spec required. There is a minor compatibility risk as the second input would disappear in this case (table-column ~= display:none).
  
  
• (2) We want to ignore display:table-* on replaced elements if their parent is not display:table|inline-table. We can mention this as an effect similar to the blockification of flex/grid which happens before tables fixup.

Opinions?

[FremyCompany]

Follow up: for the <button> tag, Edge does apply table-column as intended by the spec, but not the other browsers. See https://jsfiddle.net/p24k4q54/. I can almost sense a common theme here ;-)