- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Mar 2023 21:13:24 +0000
- To: public-css-archive@w3.org
Interesting, that's option 4, using a special case for the resolution of `<percentage>` in the context of ranges.
I think that will somewhat cripple this feature when used in conjunction with layout.
For example, this is easy when used with `px`:
```css
.source {
position: absolute;
top: 10px;
animation-timeline: view();
animation-range: contain 0% exit -10px;
}
```
But becomes tricky when used with `%`:
```css
.source {
position: absolute;
top: 10%;
animation-timeline: view();
animation-range: contain 0% exit -10%;
}
```
In this case `10%` is computes to different values for `top` and `animation-range`.
--
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8557#issuecomment-1464480920 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 March 2023 21:13:26 UTC