W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-text-3] Audit details of break-spaces value against use cases

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jun 2018 17:03:16 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-400757345-1530118995-sysbot+gh@w3.org>
The Working Group just discussed `Audit details of break-spaces value against use cases`, and agreed to the following:

* `RESOLVED: Accept the proposal in https://github.com/w3c/csswg-drafts/issues/2465#issuecomment-400171764`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Audit details of break-spaces value against use cases<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2465#issuecomment-400171764<br>
&lt;dael> florian: Reopening.<br>
&lt;dael> florian: We discussed for 3 years having a value called break-space on the overflow. Chrome and Igalia are mid-impl. Current syntax is not ideal. Would like to change it. I'm not enthusiastic, but their proposal is as good as what we've written and it's to impl so I'm in favor<br>
&lt;dael> fantasai: Proposal came from discussion with me and koji where koji said prop that takes multi values is harder then one value. Requested long hands so one can take break-word and the other break-space. Reason for sep prop is if they need to cascade sep. That does seem to be the case for these values. I can see why break-spaces and break-rulew ould be different<br>
&lt;dael> fantasai: Also notices break-spaces is only ever set with pre-wrap on whitespace. You'll never cascade independantly. Makes sense to move this from overflow-wrap to whitespace prop and then it would be mutually exclusive keywords<br>
&lt;dael> fantasai: That's how got ot proposal<br>
&lt;dael> fantasai: Improvement to cascade behavior. We're cascade independantly things that can be independant. I'm in favor of proposal<br>
&lt;dael> florian: So am I, koji , and Javier<br>
&lt;fantasai> s/independent/and not things which can't/<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Accept the proposal in https://github.com/w3c/csswg-drafts/issues/2465#issuecomment-400171764<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2465#issuecomment-400757345 using your GitHub account
Received on Wednesday, 27 June 2018 17:03:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 08:16:45 UTC