- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Apr 2021 16:15:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-display] math/inline-math (whether display:math on a non-MathML context should be more inline or block)`, and agreed to the following: * `RESOLVED: have display:math behave as mrow and ping a11y to see if that's an issue` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-display] math/inline-math (whether display:math on a non-MathML context should be more inline or block)<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5385<br> <dael> astearns: Has been waiting on math people to weigh in. afaict all we need to deal with is display:math on non-MathML<br> <dael> fantasai: Decided it should be inline<br> <dael> fantasai: Issue from mozilla is having it behave different if in MathML context or not is not great. Not difficult to impl but more tricky b/c context sensitive. Not necessary for any reason.<br> <dael> fantasai: Mats asked for it to behave like em row regardless of if on math element or not<br> <fantasai> s/em row/mrow/<br> <dael> emilio: and discussion of if need >1. Supposed to be magic depending on valid. If not might need more than one<br> <fantasai> s/valid/element/<br> <dael> florian: Assume behavior of making it an em which doesn't contain math is well defined?<br> <dael> iank_: Yeah, triggers em row layout algo<br> <fantasai> s/em row/mrow/<br> <dael> iank_: In simple terms layout things on a row and I think baseline align all<br> <dael> iank_: I think mathml defines internal types fine. Sometimes mrow if it has more children than expected.<br> <dael> iank_: I think not having talked to the MathML people I htink I am supportive of adding each display type as FF folks suggest. Seems consistent with everything else. Would like to hear other thoughts.<br> <dael> iank_: Also works with polyfill story<br> <dael> fantasai: Two issue. One is display:math outside mathML is mrow behavior. Second is add more display types per mathML element<br> <dael> plinss: I think have precedent to jsut rely on display property. I would like to see all math in layout not rely on semantics<br> <dael> plinss: Have it default style<br> <dael> iank_: If you put display:grid on mrow it has an internal layout type of grid algo. Have consistency there<br> <dael> florian: Do we need to check with a11y people, a11y tree, to see if the way the build right now will break? My understanding is for some things they build from box rather than element tree. We should check. I don' tknow<br> <dael> florian: We've been accused of being careless about this in the past<br> <dael> florian: I hope it doesn't. In theory I support plinss<br> <dael> plinss: Agree worth investigating. Might justify a bug on AT. We can evaluate when we find out answers<br> <dael> astearns: Sounding like consensus to have display:math always behave as mrow<br> <dael> fantasai: Outside MathML context and unless otherwise specified<br> <dael> astearns: Prop: have display:math behave as mrow and ping a11y to see if that's an issue<br> <dael> RESOLVED: have display:math behave as mrow and ping a11y to see if that's an issue<br> <dael> astearns: Separate issue for other math display types?<br> <dael> fantasai: I believe there is<br> <dael> astearns: Is there consensus to resolve that now or postpone to future meeting?<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5385#issuecomment-819641982 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 April 2021 16:15:18 UTC