Re: [csswg-drafts] [css-text-decor] Consider adding an `all` value to `text-decoration-skip-ink` (#4277)

The CSS Working Group just discussed ``[css-text-decor] Consider adding an `all` value to `text-decoration-skip-ink` ``, and agreed to the following:

* `RESOLVED: Change the new property to be 'all' not 'always'`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-text-decor] Consider adding an `all` value to `text-decoration-skip-ink`<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4277<br>
&lt;dael> fantasai: Jonathon Kew had question on name and wanted to ask about changing from always back to all. Current value is auto and none. Adding a new keyword, options currently are always and all. Open to another idea<br>
&lt;dael> myles: No preference<br>
&lt;dael> astearns: Given that we can't change none I see jensimmons saying all works better with none<br>
&lt;dael> smfr: Prefer all<br>
&lt;dael> smfr: Always sounds more temporal. All is skip all ink. It's not sometimes or always skip ink<br>
&lt;dael> astearns: Anyone want to stick with always?<br>
&lt;dael> jensimmons: Do we use 'always' anywhere?<br>
&lt;dael> fantasai: Page breaking controls, always and avoid<br>
&lt;dael> jensimmons: Do we use 'all' a lot?<br>
&lt;dael> TabAtkins: Transition property takes all<br>
&lt;tantek> is there a reverse-index of property values to property names?<br>
&lt;dael> fantasai: Break-before and -after takes always. Transitions takes all<br>
&lt;dael> dbaron: Column-span takes all, user-select takes all<br>
&lt;dbaron> ... pointer-events, text-combine-upright<br>
&lt;dael> astearns: Less about consistency with other properties and more to make sense of values with this property and I'm convinced 'all' works better<br>
&lt;dbaron> ... transition-property<br>
&lt;dael> astearns: Sounds like it's switch to all. Objections to hange new value to 'all'?<br>
&lt;dael> RESOLVED: Change the new property to be 'all' not 'always'<br>
</details>


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

Received on Wednesday, 19 February 2020 17:52:21 UTC