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

Re: [csswg-drafts] [css-sizing] Incorrect use of the word "compute" in definition of intrinsic keyword values

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jun 2018 16:58:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-400755420-1530118738-sysbot+gh@w3.org>
The Working Group just discussed `Incorrect use of the word "compute" in definition of intrinsic keyword values`, and agreed to the following:

* `RESOLVED: change to "behave as" instead of "compute"`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Incorrect use of the word "compute" in definition of intrinsic keyword values<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2708<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/commit/b603bfb33da70080b83f78e74f41c8af89b9b88b<br>
&lt;dael> fantasai: Changes are ^<br>
&lt;dael> fantasai: The min content and max content keywords and that type are currently defined to behave as property initial value if spec in block axis.<br>
&lt;dael> fantasai: Spec says they compute to property initial value so auto on height or none or max-height.<br>
&lt;dael> fantasai: Mats would prefer it to say "bahevs as" rather then "computes to"<br>
&lt;dael> fantasai: TabAtkins and I have no strong opinion. Up to impl.<br>
&lt;dael> s/bahevs/behaves<br>
&lt;dael> fantasai: Example from Mats is if you explicitly inherit height and gave one of these keywords you should get that keyword. Makes sense, but can't imagine anyone inheriting height.<br>
&lt;dael> dbaron: Issue is impl have to impl what spec says and that can be a pain to do<br>
&lt;dael> florian: If no real use case and simplier thing to impl, why not?<br>
&lt;dael> dbaron: Note one interesting point that request is the opposite of the request a few issues ago.<br>
&lt;dael> fantasai: Yep<br>
&lt;emilio> https://bugs.chromium.org/p/chromium/issues/detail?id=850872 is a broken site for inheriting height fwiw :-)<br>
&lt;dael> dbaron: Maybe figure out underlying principle. Maybe if it's a property that effects type of boxes.<br>
&lt;dael> Rossen_: Any reasons to not word it as "behaves as"?<br>
&lt;dael> Rossen_: I sympathize with Mats and having dependency between properties when computing the value of others is usually a thing to avoid. By not being a strict as current wording it at least doesn't explicitly say this is what it is.<br>
&lt;dael> Rossen_: We're not fixing issue by changing wording<br>
&lt;dael> Rossen_: For current sizing spec, are we okay make the change to "behave as" instead of "compute"<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> fremy: Wasn't change to revert?<br>
&lt;dael> Rossen_: revert what?<br>
&lt;dael> fantasai: Resolution asked is to accept the change<br>
&lt;dael> florian: Reverse is earlier issue<br>
&lt;dael> Rossen_: I said change to behave as instead of compute.<br>
&lt;dael> RESOLVED: change to "behave as" instead of "compute"<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2708#issuecomment-400755420 using your GitHub account
Received on Wednesday, 27 June 2018 16:59:05 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 September 2019 01:18:58 UTC