- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jul 2022 19:34:21 +0000
- To: public-css-archive@w3.org
> One point to keep in mind is that MathML isn't really its own separate rendering context like SVG - it relies various parts of CSS/HTML today. For example `<mtable>`, `<mtd>`, `<mtr>`, etc. Today each of those will compute to `table`, `table-cell`, `table-row` respectively. @bfgeek In Gecko at least, `mtable` and so compute to `display: table-*`, but mostly as an implementation detail, since we share a bunch of code with HTML tables... But they are, afaict, the exception rather than the rule. > @emilio What are you advocating for? To make each of the algorithms have a separate display type? Or no special value at all? I think having a magic `math` value that works only on MathML elements isn't much different from what e.g. SVG does (where `display` isn't generally honored, other than `none`). What advantage does it give you to have a `math` value, compared to just "assume `display` is `math` if it's not `none`" (which is roughly what SVG does)? Also, in that case, how do MathML elements with non-`math` values behave, and is it useful to make them behave in that way? -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5866#issuecomment-1188216899 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 July 2022 19:34:23 UTC