Re: [csswg-drafts] [css-display] math/inline-math (#5385)

The CSS Working Group just discussed `math/inline-math redux`, and agreed to the following:

* `RESOLVED: to ammend our previous resolution to follow the ruby model and use 2 values only/defaults to inline, as is suggested in the issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: math/inline-math redux<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/5385#issuecomment-692735088<br>
&lt;fantasai> +1 to mats's suggestion<br>
&lt;bkardell_> fredw: (asking for clarity)<br>
&lt;oriol> +1 to mats<br>
&lt;bkardell_> fantasai: so the default would be that math is inline, and you could say block<br>
&lt;bkardell_> fredw: I think this is related to iank_ suggestions about adding support for the legacy syntax<br>
&lt;bkardell_> fredw: I guess part of the rationale was also that the 2 value syntax isn't supported by all browsers yet<br>
&lt;iank_> I think generally it makes sense for inline-math just for the purposes of that's what web developers are used to expect. :)<br>
&lt;bkardell_> fantasai: I think really it was just about consistency -- he was saying, or tab was saying - there is value for authors in maintaining the consistency since it is a minor add<br>
&lt;bkardell_> faceless2:  It would mean you couldn't get it implemented/tested until you had 2 value support in all of the browsers<br>
&lt;bkardell_> fantasai: you could 1 off implement it just for this, but I dont think that would be a good idea. I don't think the parsing problems are diffiult, it's just that there hasn't been a strong motivation for anyone to do it<br>
&lt;bkardell_> fredw: I am curious how you would get block math without supporting this?<br>
&lt;bkardell_> astearns: you couldn't<br>
&lt;NeilS> bkarell: we would like to keep the legacy keyword, right?<br>
&lt;NeilS> fantasai: block-math?<br>
&lt;bkardell_> bkardell_: right: ... nevermind that doesn't make sense<br>
&lt;NeilS> fanstasi: if you ask the chrome team, they probably will tell you that the two keyword version just hasn't been a priority<br>
&lt;bkardell_> chrishtr: I am not concerned about it<br>
&lt;fantasai> s/chrishtr/cbiesinger/<br>
&lt;bkardell_> fredw: I think the parsing is probably easy but then we have to store the value internally and serialize it<br>
&lt;bkardell_> emilio: it's super easy, I know the chrome code for this - it's very easy<br>
&lt;bkardell_> fredw: ok so I guess it should be easy<br>
&lt;bkardell_> oriol: &lt;something><br>
&lt;bkardell_> astearns: I think I am hearing consensus to follow the ruby model and use 2 values only/defaults to inline<br>
&lt;oriol> s/&lt;something>/I agree it should be easy/<br>
&lt;bkardell_> fredw: what does the serialization look like?<br>
&lt;bkardell_> fantasai: you serialize to the shortest form, so it will serialize as display: math or display: block math<br>
&lt;bkardell_> RESOLVED: to ammend our previous resolution to follow the ruby model and use 2 values only/defaults to inline, as is suggested in the issue<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-694369213 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 17 September 2020 17:03:50 UTC