Re: [csswg-drafts] [css-fonts-4] font-variant-emoji property lacks an unopinionated, standardized default

The Working Group just discussed `font-variant-emoji property lacks an unopinionated, standardized default`, and agreed to the following:

* `RESOLVED: Have auto follow platform conventions and add a new value called unicode to follow unicode conventions`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: font-variant-emoji property lacks an unopinionated, standardized default<br>
&lt;chris> q+<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1223<br>
&lt;astearns> ack chris<br>
&lt;dael> chris: Basically the thing with this is we describe auto which tries to do 2 things. User agents may follow unicode or ignore them and do what platform does. Seems like 2 use cases and you'll have UA and platform variations. Some people might want to say unicode is what we want, but you can't do that. You can say mostly I have text or mostly I have emoji. WE lack a 4th value that says do what unicode does<br>
&lt;dael> myles: I thinkt he idea of a new value is fine. It's fairly important that our default matches platfor so I agree can't be default, but a new value for follow unicode is fine<br>
&lt;dael> chris: myles does that sound like it has impl complexity?<br>
&lt;chris> ok<br>
&lt;dael> myles: I don't think that much. Prop has some complexity, but additional complexity isn't much bigger<br>
&lt;dael> myles: Can't speak for other browsers<br>
&lt;chris> other immplementors?<br>
&lt;dael> astearns: Do we also need a follow platform?<br>
&lt;dael> myles: Isn't that what auto is?<br>
&lt;dael> chris: At the moment auto isn't clear, but it I agree ti should be do what the platform does. THat's closes to current impl<br>
&lt;dael> myles: Sounds good<br>
&lt;dael> astearns: All engines or is there an engine that's been taking ambig in spec and it follows unicode<br>
&lt;dael> myles: As far as I know there are 0 impl<br>
&lt;dael> astearns: Prop: Have auto follow platform conventions and add a new value to follow unicode conventions<br>
&lt;chris> bikeshed the name?<br>
&lt;dael> fantasai: Call it normal? The new one. Auto is more magic, normal is follow a convention. There's prob a better name<br>
&lt;dael> myles: Unicode? OR resolve without name?<br>
&lt;dael> chris: Let's not resolve unless we're stuck. I think unicode is better<br>
&lt;dael> astearns: Objections to unicode as the name?<br>
&lt;dael> astearns: Prop Have auto follow platform conventions and add a new value called unicode to follow unicode conventions<br>
&lt;dael> RESOLVED: Have auto follow platform conventions and add a new value called unicode to follow unicode conventions<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1223#issuecomment-409760079 using your GitHub account

Received on Wednesday, 1 August 2018 23:43:06 UTC