- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Sep 2020 17:23:39 +0000
- To: public-css-archive@w3.org
@fred-wang It's hardly anything in terms of spec work, not more complicated than saying it computes to `flow`. And in terms of tests, we need a test for what happens with these display values on non-MathML elements either way -- proving that it renders as `flow` rather than `mrow` is roughly equivalent to proving that it renders as `mrow` rather than `flow`. As for implementations, in Gecko at least I believe it's actually easier to map a `display` value to a box type unconditionally than to make it compute to a different value depending on its namespace/ancestry and I'd be surprised if the same isn't true for WebKit and Blink. The `<math>` element itself is following the same codepath we're proposing for `<div>` so by making them the same, we are not adding any new code path, only removing the exception for elements outside of MathML context. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5385#issuecomment-699663086 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 September 2020 17:23:40 UTC