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

Re: [csswg-drafts] How to refer to the corner-shaped padding/border/content edges (#5132)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Oct 2020 23:55:30 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-705252886-1602114929-sysbot+gh@w3.org>
The CSS Working Group just discussed `How to refer to the corner-shaped padding/border/content edges`, and agreed to the following:

* `RESOLVED: Add these terms but bikeshed names in GH issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: How to refer to the corner-shaped padding/border/content edges<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5132<br>
&lt;dael> florian: A little while back, I believe in context of layout containment, I needed to refer to border edge with its rounded corners if they're rounded or with any future shaping. Couldn't figure out if border-edge implied the shaping or if you need something else<br>
&lt;dael> florian: Backgrounds 4 suggests it is themselves shaped but other specs say it's a rectangle. Worth having two terms for the shaped and unshaped so can be specific. Keep the existing term so if it doesn't matter don't have to spec<br>
&lt;dael> florian: I think helpful b/c specs which have taken time to say with the rounded corners would have to expand if we added another edge.<br>
&lt;dael> florian: Proposal is shaped edge and unshaped edge defintion maybe in Box 4<br>
&lt;dael> smfr: Prefer to avoid confusion with other properties that use shape<br>
&lt;dael> florian: Sure. Not attached to the adjective. Just want terms to refer to either<br>
&lt;dael> smfr: Rounded?<br>
&lt;dael> florian: Rounded is what we have now. If we do bezeled or notched they're not rounded be effect the corners<br>
&lt;dael> Rossen_: Can we refer to unshaped corner as bounds. border-bounds, content-bounds which is the rectangle?<br>
&lt;dael> astearns: Padding border content edge bounds?<br>
&lt;dael> fantasai: A bit confusing with terms for fragmented boxes, though<br>
&lt;dael> Rossen_: Too many terms :)<br>
&lt;dael> Rossen_: I should be applying padding bounds.<br>
&lt;dael> florian: Not attached to particular adjective but I think it should be adj on edge. Mention edge all over the place and sometimes mean with and somethings without. Adding an adjective to edge is easier because then we can amend existing text instead of review all specs and making sure not wrong one<br>
&lt;dael> florian: Overall hearing support for idea but not for the bikeshed color so should we go back to GH or twitter and ask for ideas?<br>
&lt;dael> astearns: Don't know if this is useful on twitter since it's a spec term<br>
&lt;dael> florian: True<br>
&lt;dael> Rossen_: I think letting more people chime in on GH is worthwhile<br>
&lt;dael> astearns: Prop: Add these terms but bikeshed names in GH issue<br>
&lt;dael> astearns: Any concerns about adding? Objections?<br>
&lt;dael> fantasai: Good as long as florian mentions base term is same<br>
&lt;dael> RESOLVED: Add these terms but bikeshed names in GH issue<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 October 2020 23:55:32 UTC

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