Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363)

The CSS Working Group just discussed `[motion-1] the description of contain flag in ray() function`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> TabAtkins: Unless people agree with me, I don't expect resolution but want eyes. Motion is in interop 2023 and have issues<br>
&lt;dael> TabAtkins: Problem is the ray function was added to make it easy to put things around a circle. Wanted easy way to postion around the edge of a watch face.<br>
&lt;dael> TabAtkins: Have origin out to some distance. Element is along a 0-100% path. 100% is edge of the watch face but you want to pull it in and not have the center at 100%.<br>
&lt;dael> TabAtkins: We had the contain flag which would shorten the ray for that. Definition was pretty complicated and even ignoring the math I think it's not good based on complications<br>
&lt;dael> TabAtkins: Have suggestion to simplify at end that would have little change in practice, but better behavior in general. Better animation and more predictable.<br>
&lt;dael> TabAtkins: If anyone has opinions would like them in thread. If I don't hear for a while I'll add to spec<br>
&lt;dael> TabAtkins: Summary is previously took rectangle of eleemnt and pulled in until it's in circle defined by what the ray projects into. Figuring out how much to pull a square into the circle is not trivial. The angle mattered which made positioning weird.<br>
&lt;dael> TabAtkins: Now is treat element like a circle based on larger dimension. Circle to circle make is way easier<br>
&lt;Rossen_> q?<br>
&lt;dael> TabAtkins: Don't need resolution right now, but want attention.<br>
&lt;dael> Rossen_: Thoughts or feedback?<br>
&lt;dael> fantasai: This was supposed to also handle non-circular watches. Is that still doing that or does it only work for circles?<br>
&lt;dael> TabAtkins: Should generally do it. Especially if element you're trying to postion is square should work approx same. Rectangle will be a bit different. Old if you're positioning rectangle to rectangle you would get right at the edge. But that's not the original thing it was trying to solve. Mine gives you good on circle and okay on rectangle<br>
&lt;dael> fantasai: Would be good to get people that do watch stuff to take a look. I'll look also<br>
&lt;dael> Rossen_: Feedback here is general temp is positive to proceed forward. I guess that's what you're looking for<br>
&lt;dael> fantasai: I think we should bring it back once we have spec text to resolve on. People should review with examples and stuff<br>
</details>


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


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

Received on Thursday, 2 March 2023 00:11:02 UTC