- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2023 13:20:47 +0000
- To: public-css-archive@w3.org
Summary for CSSWG: Problem: - When we capture the content of old views, we don't know how they might be animated. - Parts of the element currently out-of-view may animate into view during the transition. - Some elements are so large, we cannot feasibly capture all of it. Imagine capturing the `<body>` of the HTML spec. Proposal: - The dimensions of the group is still based on the size of the element. - UAs don't need to capture pixels of the views. - They must at least capture the area currently within view. - They should capture more than this, to account for animations involving position. Questions: - Is it ok to leave the actual area of calculation down to UAs? That way, the area captured can differ depending on device constraints. - What should the natural width/height of the old/new views be in these cases? - Can this behaviour be otherwise script-visible? -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8561#issuecomment-1470001908 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 March 2023 13:20:49 UTC