Re: [csswg-drafts] [css-text] Control characters

The Working Group just discussed `Shipping visible Cc`, and agreed to the following resolutions:

* `RESOLVED: clarify spec to say these characters should be always visible`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Shipping visible Cc<br>
&lt;fantasai> https://drafts.csswg.org/css-text-3/issues-lc-2013#issue-161<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1990<br>
&lt;dael> astearns: This time we'll syncronize.<br>
&lt;dael> myles: didn't have a date and it failed. Maybe we just shouldn't do it- show them visible.<br>
&lt;dael> fantasai: We need it all impl behind a flag and then all flip on.<br>
&lt;dael> myles: That's fair, but has always been true.<br>
&lt;dael> fantasai: Didn't some people release?<br>
&lt;dael> florian: They impl something...not what we speced?<br>
&lt;myles> s/Maybe we just shouldn't do it- show them visible./We shouldn't show them visibly/<br>
&lt;dael> fantasai: Comment from me was we wanted to coordinate shipping this together so that authors know it's an intentional thing for the platform.<br>
&lt;fantasai> s/from me/from xidorn/<br>
&lt;dael> eae: For us it's font dependant. If the font has a glyph it shows.<br>
&lt;dael> myles: I think that's what we do too.<br>
&lt;dael> astearns: So people sync shipping things...<br>
&lt;astearns> s/things/thiiinnngs<br>
&lt;dael> fantasai: Previous spec said control characters are invisible. People wanted it visible, I changed the spec, we were going to coordinate and it shipped.<br>
&lt;dael> eae: WE had a flag and there was a rough time peroid.<br>
&lt;dael> fremy: We were supposed to do it and we did not.<br>
&lt;dael> fantasai: I think goal was ship on a particular day. Anyone who shipped on proposed schedule had no one with them.<br>
&lt;dael> astearns: However this happened. What's before us right now is how to deal with spec. Do we leave it in that we want control characters visible? Change spec to match what's interop?<br>
&lt;dael> florian: We no longer have full interop. Some browsers are visible or not depending on font.<br>
&lt;dael> astearns: Any browsers always visible?<br>
&lt;dael> florian: I think that's behind FF flag.<br>
&lt;dael> astearns: Edge has not shipped it.  Safari?<br>
&lt;dael> myles: [missed]<br>
&lt;dael> florian: Blink basic font for windows has control characters so it's there but on iOS it doesn't so they're not.<br>
&lt;dael> Rossen: We shipped when we said it would.<br>
&lt;dael> fremy: Did we?<br>
&lt;dael> fantasai: We have 2 interop impl on windows.<br>
&lt;fantasai> I didn't say anything<br>
&lt;dael> dbaron: Based on what I'm reading FF nightly has had it on for a while.<br>
&lt;dael> astearns: This being in the spec is not gated on the simultaious shipping.<br>
&lt;dbaron> (though I'm less sure than usual that I'm reading correctly since somebody just rewrote a bunch of pref stuff...)<br>
&lt;dael> florian: Clarify spec that we mean visible visible.<br>
&lt;dael> ??: What character do you use<br>
&lt;dael> fantasai: Your default.<br>
&lt;fantasai> s/Your default/missing glyph replacement/<br>
&lt;dael> florian: You put a visible thing so people fix it.<br>
&lt;dael> astearns: So this issue is basically close and clarify that it should be visible. But the coordination convo is not relelvent<br>
&lt;dael> astearns: Objections to clarify spec to say these characters should be always visible ?<br>
&lt;xidorn> (dbaron: I just had a look at the code and I don't think we enable it right now on nightly)<br>
&lt;dael> eae: First browser will look broken. It'll be worse if we force to always. I'm not opposed but a little unpleasent.<br>
&lt;dael> astearns: Still better if coordinate<br>
&lt;dael> RESOLVED: clarify spec to say these characters should be always visible<br>
&lt;dbaron> xidorn, layout.css.control-characters.visible seems to be enabled<br>
</details>


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

Received on Wednesday, 11 April 2018 12:50:54 UTC