W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

Re: [csswg-drafts] [css-transforms] Spec and blink implementation of transform-box for SVG elements differ

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Apr 2017 01:15:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-295526926-1492650911-sysbot+gh@w3.org>
The CSS Working Group just discussed border-box vs view-box in transform-box, and agreed to the following resolutions:

```
RESOLVED: Add "auto" as initial value for transform-box, give it the current border-box/view-box dual behavior
```

```
RESOLVED: Add stroke/padding/content-box, and set up the proper mappings between them for transform-box.
```

<details><summary>The full IRC log of that discussion</summary>

```
<TabAtkins> Topic: border-box vs view-box in transform-box
<TabAtkins> GitHub Topic: https://github.com/w3c/csswg-drafts/issues/857
<TabAtkins> TabAtkins: I have an action to review the CSS <=> SVG box keyword mappings and find a consistent mapping between them.
<TabAtkins> TabAtkins: This one (border-box = view-box) is particularly bad; border-box normally equals stroke-box.
<TabAtkins> TabAtkins: I suspect it was done solely to give us an initial value that captured the diff between CSS and SVG.
<TabAtkins> Rossen: So is that a spec bug?
<TabAtkins> TabAtkins: Yeah. We should make border-box work properly. Then add a new initial value (auto?) that still captures the dual-behavior we want.
<TabAtkins> Rossen: Objections?
<TabAtkins> smfr: Ah yeah, they're bending what border-box means right now.
<TabAtkins> RESOLVED: Add "auto" as initial value for transform-box, give it the current border-box/view-box dual behavior
<TabAtkins> TabAtkins: Further issue here - spec maps fill-box to border-box. That violates the mapping used elsewhere in CSS, where border=stroke and padding/content=fill.
<TabAtkins> TabAtkins: Suspect it was just because there's only use-cases for those two, and they're close enough that they wer ejust mapped for convenience. But that's inconsistent and bad for the platform.
<TabAtkins> TabAtkins: Should we add the additional box keywords and set up a proper mapping?
<TabAtkins> RESOLVED: Add stroke/padding/content-box, and set up the proper mappings between them for transform-box.
```
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/857#issuecomment-295526926 using your GitHub account
Received on Thursday, 20 April 2017 01:15:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:11 UTC