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

Re: [csswg-drafts] [css-transform] the used value for border-box

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Jun 2018 17:01:07 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-398823684-1529514066-sysbot+gh@w3.org>
The Working Group just discussed `the used value for border-box`, and agreed to the following:

* `RESOLVED: add these keywords to transform-box property`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: the used value for border-box<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/999#issuecomment-391431901<br>
&lt;dael> krit: transform-box has a couple fo defined boxed. Issue is we have mapping defined for fill and stroke fallbacks. THe mapping between html and svg boxes it request more values to supported value of transform-box. border-box on svg fallsback to stroke-box but we don't have that exposed.<br>
&lt;dael> krit: Proposal is every fallback we define would also be definable on transform. We'd add content box and stroke box<br>
&lt;dael> smfr: Which spec will define the boxes?<br>
&lt;dael> krit: Each spec defines mapping.<br>
&lt;dael> fantasai: It would be fine to import the mapping to transform spec as it's more mature then fill/stroke<br>
&lt;dael> krit: Currently transform and masking do what we defined for fill/stroke. We're adding the keywords for the spec behavior so users can spec directly<br>
&lt;dael> astearns: Concerns with adding these values?<br>
&lt;dael> fantasai: sgtm<br>
&lt;dael> smfr: I think I'm okay with [missed]<br>
&lt;dael> astearns: Sounded like smfr if okay but is not sure transforms is right place for dfinitions<br>
&lt;dael> fantasai: Not sure where else. I guess fill/stroke is fine<br>
&lt;fantasai> s/fine/fine, but it's a very early-stage WD/<br>
&lt;dael> krit: That's why masking and transform already define it, but they do it the same way<br>
&lt;dael> astearns: Given things move in different velocities we may defer to fill and stroke in a future transforms<br>
&lt;dael> astearns: Objections to add these keywords to transform-box property?<br>
&lt;dael> RESOLVED: add these keywords to transform-box property<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/999#issuecomment-398823684 using your GitHub account
Received on Wednesday, 20 June 2018 17:01:10 UTC

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