Re: [fxtf-drafts] [motion-1] anchor-position - which box? (#503)

The CSS Working Group just discussed `[motion-1] anchor-position - which box?`, and agreed to the following:

* `RESOLVED: default box used by 'auto' value of 'offset-anchor' is box specified by 'transform-box', so it matches box used by 'transform-origin'`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: Most offset stuff refers to containing block for sizing/positioning<br>
&lt;fantasai> TabAtkins: exception is offset-anchor, which specifies point that anchors to the path<br>
&lt;fantasai> TabAtkins: This needs to refer to one fo the element's boxes<br>
&lt;fantasai> TabAtkins: spec just says "a box"<br>
&lt;fantasai> TabAtkins: doesn't say which one<br>
&lt;fantasai> TabAtkins: the obvious one would be to use border box<br>
&lt;fantasai> TabAtkins: but since it's a transform, might want to synch up with other transforms<br>
&lt;fantasai> TabAtkins: I suggest using 'transform-box' property<br>
&lt;fantasai> TabAtkins: This would also default it to border-box, because that's what 'transform-box' defaults to, which is good<br>
&lt;fantasai> TabAtkins: but it would let you match, if you change the transform thing<br>
&lt;fantasai> florian: Seems reasonable<br>
&lt;fantasai> PROPOSED: default box used by 'auto' value of 'offset-anchor' is box specified by 'transform-box', so it matches box used by 'transform-origin'<br>
&lt;fantasai> astearns: objections?<br>
&lt;fantasai> RESOLVED: default box used by 'auto' value of 'offset-anchor' is box specified by 'transform-box', so it matches box used by 'transform-origin'<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 13 March 2023 14:28:25 UTC