Re: [fxtf-drafts] [motion-1] offset-anchor:auto is nonsensical (#502)

The CSS Working Group just discussed `[motion-1] offset-anchor:auto is nonsensical`, and agreed to the following:

* `RESOLVED: offset-anchor:auto uses transform-origin point`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: the def of offset-anchor: auto just copies over the offset-position value if that's not auto<br>
&lt;fantasai> TabAtkins: the reason for this was, if you specify offset-anchor: auto; offset-position: %<br>
&lt;fantasai> TabAtkins: then you would get a behavior similar to background--position<br>
&lt;fantasai> TabAtkins: where 100% put the element at the bottom right edge<br>
&lt;fantasai> TabAtkins: that's not unreasonable<br>
&lt;fantasai> TabAtkins: but if offset-position is not using percentages, you interpret 100px e.g. relative to the element's own box<br>
&lt;fantasai> TabAtkins: which means the element doesn't move at all!<br>
&lt;fantasai> TabAtkins: that's really weird behavior and definitely unintended<br>
&lt;fantasai> TabAtkins: it's also not necessary if we do the other fix if we do the other fix of starting from offset-anchor<br>
&lt;fantasai> TabAtkins: if you want bottom right corner, you set both to the same value<br>
&lt;fantasai> TabAtkins: very simple to get this behavior without the weird hack<br>
&lt;fantasai> TabAtkins: so propose to drop this behavior, offset-anchor: auto just uses tranform-origin<br>
&lt;fantasai> TabAtkins: since we need a default value, and good chance you'll want to use the same transform-origin as other transforms<br>
&lt;fantasai> florian: ???<br>
&lt;fantasai> TabAtkins: ....<br>
&lt;fantasai> astearns: any objections?<br>
&lt;fantasai> RESOLVED: offset-anchor:auto uses transform-origin point<br>
&lt;florian> s/???/in all cases, or just when offset-position is not using %?/<br>
&lt;florian> s/..../in call cases/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/502#issuecomment-1466262406 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:37:10 UTC