Re: [csswg-drafts] [scroll-animation-1] Define scroll linked animation behavior in printing documents (#8226)

The CSS Working Group just discussed `[scroll-animation-1] Define scroll linked animation behavior in printing documents`, and agreed to the following:

* `RESOLVED: for printing/paged, root is considered fully in view (scroll timelines on it are inactive)`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> flackr: When you print a doc, we need to define what the animation value from SLA is<br>
&lt;TabAtkins> flackr: I think there's two possible choices.<br>
&lt;TabAtkins> flackr: I think makes the most sense is to treat the root as a scroller that's fully in view - scrollport is size of scrollable area<br>
&lt;TabAtkins> flackr: This means many animatinos wouldn't have a time value, so they'd be skipped<br>
&lt;florian> q+<br>
&lt;TabAtkins> flackr: Other option is we treat one page as the scrollport, and presumably the scroll position is zero<br>
&lt;astearns> ack florian<br>
&lt;TabAtkins> florian: I'm not on top of things wrt animations, but wanted to point out that while it's not common, print and paged can be different - you can have scrollable things in a page in ebook, for example<br>
&lt;fantasai> TabAtkins: I think this question is for the root scroller though<br>
&lt;fantasai> TabAtkins: which is basically the same problem for paged and print<br>
&lt;TabAtkins> flackr: other scrollers are fine, they can compute their time. this is just the root scroller<br>
&lt;TabAtkins> flackr: it just doesn't really have a scroll position<br>
&lt;TabAtkins> fantasai: Can you explain more? say i have a root backgroudn animation from green to red as it goes 0%-100%. what happens when I print?<br>
&lt;TabAtkins> flackr: The scroll animation is considered inactive since there is no scrollable overflow, so it's not applied.<br>
&lt;TabAtkins> fantasai: That makes sense, I think that's the right thing to do.<br>
&lt;TabAtkins> astearns: So proposed resolution is that, for printing/paged purposes, we treat root as fully in view with no scrollable overflow<br>
&lt;TabAtkins> fantasai: scroll timeline is inactive on the root, maybe clearer to state directly<br>
&lt;TabAtkins> RESOLVED: for printing/paged, root is considered fully in view (scroll timelines on it are inactive)<br>
</details>


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


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

Received on Monday, 20 March 2023 15:26:01 UTC