Re: [csswg-drafts] [css-text-decor-4] Consider adding a third value (skip?) for text-decoration-skip-ink.

The Working Group just discussed `Consider adding a third value (skip?) for text-decoration-skip-ink`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Consider adding a third value (skip?) for text-decoration-skip-ink<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2818<br>
&lt;dael> Rossen: astearns you added this from  the F2F. I wanted to hear from Amelia or myles or anyone involved<br>
&lt;dael> myles: This is asking for a distinction between off/on/do what platform does. For us on and do platform is the same. Proposal asks for explicit on. I wanted to knwo what other vendors thought about skipping on by default<br>
&lt;dael> fantasai: I don't think it's by default. Request is a value, doesn't mean we change initial. Initial is auto.<br>
&lt;dael> Rossen: Do we need auto?<br>
&lt;dael> fantasai: Yes. Wanted to allow UA to do what it felt like.<br>
&lt;dael> myles: Cool if all browsers decided default was do skipping so we could have 2.<br>
&lt;dael> Rossen: Our position is we  just finished re-write inline layout. ink-skipping was on my shortlist, but that shortlist wasn't short so we didn't get to it. As a targetted behavior we'd want on by default once we have it. Just like w e  enable kerning by default. Doable, not super concerning for perf.<br>
&lt;dael> myles: Sounds like you're okay with 2 values<br>
&lt;dael> Rossen: Yes<br>
&lt;dael> myles: We are also happy with 2<br>
&lt;dael> Rossen: Having said that there's now ay to force it. If platform supports but if i t decides on that device it disables you can't force it.<br>
&lt;dael> myles: When you produce a product that can have that behavior we can re-open?<br>
&lt;dael> Rossen: Fine.<br>
&lt;dael> Rossen: Is Amelia on?<br>
&lt;fantasai> s/Amelia/Emilio/<br>
&lt;dael> dbaron: I don't think xidorn wanted it on for all<br>
&lt;dael> myles: Do you remember reasons?<br>
&lt;dael> dbaron: I think some w as related to what he saw as default on platform. Maybe windows primarily.<br>
&lt;dael> dbaron: Don't remember that well. Underlying was xidorn wasn't comfortable with on by default for all.<br>
&lt;dael> myles: Maybe let this go into issue and ask him  to comment in issue?<br>
&lt;emilio> Rossen: I'm on IRC fwiw (can't get on the call today :()<br>
&lt;dael> fantasai: Yeah. Can also take up on Sept 5 call<br>
&lt;dael> myles: Sounds good<br>
&lt;dael> Rossen: Sounds reasonable.<br>
&lt;dael> Rossen: Let's stop here and move on.<br>
</details>


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

Received on Wednesday, 22 August 2018 16:48:38 UTC