Re: [csswg-drafts] [css-view-transitions-2] Cross-document View Transition when there is a UA transition (#8953)

The CSS Working Group just discussed `[css-view-transitions-2] Cross-document View Transition when there is a UA transition`, and agreed to the following:

* `RESOLVED: UAs may discard author transitions if they are providing their own`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> khush: This was about, some browsers have transition as part of browser UX while navigating<br>
&lt;fantasai> khush: e.g. in Safari and Chrome today, if you swipe between pages you get default transition from UA<br>
&lt;fantasai> khush: Proposal is that if the UA does its own transition, don't do the author transition<br>
&lt;hober> q+<br>
&lt;fantasai> khush: if there's a use case where authors want to customize, could allow that somehow<br>
&lt;fantasai> khush: but don't run both<br>
&lt;fantasai> hober: I think that sounds good.<br>
&lt;fantasai> hober: I think the main case you identified on mobile is history swiping<br>
&lt;fantasai> hober: it would be bad if having two animations, so if spec allows browsers to skip transition in those cases seems fine<br>
&lt;fantasai> hober: there was a related issue wrt disabling browser animation, and I have concerns about that<br>
&lt;fantasai> astearns: Should we be more permissive and say that the UA can either skip the transition if providing their own, or somehow accommodate<br>
&lt;fantasai> hober: that would work for me too<br>
&lt;fantasai> astearns: other opinions?<br>
&lt;fantasai> astearns: proposed resolution is that UAs may discard author view transitions if they are providing their own<br>
&lt;fantasai> astearns: objections?<br>
&lt;fantasai> RESOLVED: UAs may discard author transitions if they are providing their own<br>
</details>


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


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

Received on Tuesday, 18 July 2023 18:44:08 UTC