- From: Loirooriol via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jul 2017 14:46:39 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-tables][css-display] Fixup should create inline-table when parent inlinifies == The [fix-up algorithm](https://drafts.csswg.org/css-tables-3/#fixup-algorithm) only creates an anonymous `inline-table` when the parent box is an inline box. However, this should also happen whenever the parent inlinifies its contents. It's worth noting that, according to [CSS Display](https://drafts.csswg.org/css-display-3/#transformations), inlinification happens before anonymous fix-up, so the fix-up algorithm can't rely on inlinification to make `table` become `inline-table`. Currently I think inlinification only happens in ruby containers, and run-in boxes with a `flow` inner display type. Gecko is the only proper implementation of ruby, and effectively it seems to generate an anonymous inline-table inside a ruby container. I don't know any implementation of run-ins, but a run-in with a `flow` inner display type seems to be considered an inline box (this should be clarified in #1491); so this case may already be covered by the current spec. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1590 using your GitHub account
Received on Monday, 10 July 2017 14:46:46 UTC