Re: [csswg-drafts] [css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot (#10585)

The CSS Working Group just discussed `[css-view-transitions-2] Optionally capture some properties (e.g. opacity/border) as style instead of snapshot`.

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> noamr: talked about capturing snapshots not flat but to also capture borders, shadows, opacity, etc<br>
&lt;bramus> … had homework to figure out the exact way of how this would work and do some compat analysis<br>
&lt;bramus> … have done both to an extent<br>
&lt;noamr> https://github.com/WICG/view-transitions/blob/main/nested-explainer.md#layered-capture<br>
&lt;bramus> … wrote an explainer for this<br>
&lt;bramus> … main question is if this is a net improvement to capturing elements layered or not?<br>
&lt;bramus> … only works when elements are superimposed on eachother in a way, like cross-fade morphs the animation<br>
&lt;bramus> … many people use slide animations, like a header sliding offscreen<br>
&lt;bramus> … when authors do that, capturing the borders separately creates a different effect<br>
&lt;bramus> … backwards compat it wouldnt affect hat many peole right now, but those that are affected are affected in a big way<br>
&lt;bramus> … want to get attention to the explainer<br>
&lt;bramus> … there are afew optoins:<br>
&lt;bramus> … make it an opt-in<br>
&lt;bramus> … or create an extra pseudo for the geometry animation<br>
&lt;khush> q+<br>
&lt;bramus> …  it does create more things to think about it, but nice thing about that it is that it does what it does today<br>
&lt;bramus> … you need to only style it if you want to<br>
&lt;bramus> … third option is to have no opt-in and have authors opt-out by containment thorugh adding an extra container element<br>
&lt;bramus> … not looking for a resolution now<br>
&lt;astearns> ack khush<br>
&lt;bramus> khush: +1 to what noam said<br>
&lt;bramus> … am pretty convinced that original capture way might have been a mistake.<br>
&lt;bramus> … noam dug up styles that authors used to customize animatoins and have found slight animations that were set up<br>
&lt;bramus> … if you have two things<br>
&lt;bramus> … where the whole bg changes you dont want those to fade but just want the slide effect<br>
&lt;bramus> … dont want to break those<br>
&lt;bramus> … especially on the root level<br>
&lt;bramus> … also dont want authors to have to create a wrapper around the content int root to fix that<br>
&lt;bramus> … could maybe resolve that both these modes should exist<br>
&lt;bramus> … how to select one or the other can be decided later<br>
&lt;bramus> bramus: +1 on both modes being valuable<br>
&lt;bramus> a+<br>
&lt;bramus> q+<br>
&lt;bramus> astearns: need to read explainer a bit more. wrapper made sense until khushals argument<br>
&lt;bramus> noamr: should generally avoid people to change their dom for style purposes<br>
&lt;bramus> bramus: +1<br>
&lt;astearns> ack bramus<br>
&lt;bramus> bramus: can the extra speudo give a perf benefit?<br>
&lt;bramus> noamr: not really. think of border animating<br>
&lt;bramus> … I encourage ppl to look at the explainer<br>
&lt;bramus> … especially the geometry part, because we copy over the box mode<br>
&lt;bramus> s/mode/model<br>
&lt;bramus> … also scrollbars and stuff<br>
&lt;bramus> … food for a next meeting<br>
&lt;bramus> astearns:thanks for the summary and explainer. its great to have<br>
&lt;bramus> … will summarize the breakout to the www-style list and set up async resolutions and point people to the explainer<br>
&lt;bramus> … gonna wrap up<br>
</details>


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


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

Received on Wednesday, 30 October 2024 16:00:02 UTC