W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

Re: [csswg-drafts] [css-logical-1] spec should introduce propdef table notation for logical properties (#2822)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Nov 2020 00:33:19 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-722050788-1604536398-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-logical-1] spec should introduce propdef table notation for logical properties`, and agreed to the following:

* `RESOLVED: Add an optional line in propdef table for logical property groups`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-logical-1] spec should introduce propdef table notation for logical properties<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2822<br>
&lt;dael> fantasai: Need to ID properties that belong to logical prop group<br>
&lt;dael> fantasai: ONe way is shorthand in prose but suggested we add a new link to propdef tables for proeprties part of logical property mapping group with same ID<br>
&lt;iank_> An example of only looking at the "set" of properties: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22display%3A%20-webkit-box%3B%22%3E%0A%20%20%3Cdiv%20style%3D%22-webkit-box-ordinal-group%3A%202%3B%22%3EA%3C%2Fdiv%3E%0A%20%20%3Cdiv%20style%3D%22order%3A%203%3B%22%3EB%3C%2Fdiv%3E%0A%3C%2Fdiv%3E<br>
&lt;dael> fantasai: If we do this I think it should be optional in propdef so we don't have a bunch of empty fields<br>
&lt;dael> astearns: Do you agree with oriol about in associated phsyical properties?<br>
&lt;dael> fantasai: Of course. They're part of the logical property group<br>
&lt;dael> astearns: How many specs, how many properties?<br>
&lt;dael> fantasai: B&amp;B, positioning, scroll-snap, and box are the only one effected, I think<br>
&lt;dael> fantasai: border, margin, padding, scroll snap margin and padding, inset properties<br>
&lt;dael> fantasai: Most specs not effected which is why I think when making propdef don't include unless needed<br>
&lt;oriol> overflow too<br>
&lt;dael> astearns: Opinions?<br>
&lt;dael> astearns: oriol mentioned overflow<br>
&lt;dael> fantasai: Yeah<br>
&lt;fantasai> s/effected/affected/<br>
&lt;dael> astearns: Prop: Optional line in propdef table for logical property groups<br>
&lt;dael> fantasai: Yeah. May fiddle with name.<br>
&lt;dael> heycam: I also see groups for min size and max size?<br>
&lt;dael> fantasai: Yeah, sizing also affected<br>
&lt;dael> astearns: Objections to adding a line?<br>
&lt;dael> RESOLVED: Add an optional line in propdef table for logical property groups<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 November 2020 00:33:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC