Re: [csswg-drafts] [css-view-transitions-2] Define what happens when an outbound cross-document view transition starts before rendering (#9822)

The CSS Working Group just discussed `[css-view-transitions-2] Define what happens when an outbound cross-document view transition starts before rendering`, and agreed to the following:

* `RESOLVED: If a frame hasn't even been captured yet when a nav is initiated`
* `RESOLVED: If a frame hasn't even been rendered yet when a nav is initiated, don't run a VT at all (as if there was no rule declaring one)`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> noamr: I think this one is easy<br>
&lt;TabAtkins> noamr: about what happens when we're starting an outgoing VT before the page is rendered<br>
&lt;TabAtkins> noamr: say you have render-blocking styles or scripts that are slow<br>
&lt;TabAtkins> noamr: but your at-rule has already loaded, then you navigate away before even a single frame has rendered<br>
&lt;TabAtkins> noamr: currently we'd wait until the first frame then capture it, then transition away<br>
&lt;TabAtkins> noamr: proposal is if you haven't rendered a frame, you shouldn't have an outgoing transition<br>
&lt;TabAtkins> noamr: as if you hadn't encountered the opt-in at all<br>
&lt;fantasai> TabAtkins: +1 from me<br>
&lt;khush> +1<br>
&lt;bramus> +1<br>
&lt;fantasai> +1<br>
&lt;kbabbitt> +1<br>
&lt;fantasai> TabAtkins: This only happens for script initiated? Browser UI?<br>
&lt;fantasai> noamr: You happen to see CSS opt in early, but haven't rendered the page yet<br>
&lt;fantasai> TabAtkins: What causes it?<br>
&lt;fantasai> noamr: press Back, or bookmark<br>
&lt;TabAtkins> khush: also a client-side redirect<br>
&lt;fantasai> TabAtkins: That's what I meant by script-initiated navigation<br>
&lt;fantasai> noamr: that or Back<br>
&lt;TabAtkins> miriam: any other discussion?<br>
&lt;noamr> Proposed resolution: a page that hasn't rendered yet cannot trigger cross-document view transition<br>
&lt;TabAtkins> RESOLVED: If a frame hasn't even been captured yet when a nav is initiated<br>
&lt;TabAtkins> RESOLVED: If a frame hasn't even been rendered yet when a nav is initiated, don't run a VT at all (as if there was no rule declaring one)<br>
</details>


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


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

Received on Monday, 12 February 2024 19:15:32 UTC