Re: [csswg-drafts] [css-view-transitions-2] Should ViewTransitions be triggered for reloads? (#8784)

The CSS Working Group just discussed `[css-view-transitions-2] Should ViewTransitions be triggered for reloads?`, and agreed to the following:

* `RESOLVED: Reloads don't trigger view transitions by default.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> noamr: This is about reloads, came up by people using the current experiment we have with cross-document ransitions<br>
&lt;fantasai> noamr: question is what should happen on reloads<br>
&lt;fantasai> noamr: by default, currently, the transition happens<br>
&lt;fantasai> noamr: because it's just a same-origin navigation where both pages opt in!<br>
&lt;fantasai> noamr: but developers find this confusing<br>
&lt;fantasai> noamr: in the future we might want opting in or customizing specifically the reload transition<br>
&lt;fantasai> noamr: which is something we wanted to add to the opt in<br>
&lt;fantasai> noamr: but wanted to say that they're disabled for now<br>
&lt;fantasai> noamr: because more confusing that useful<br>
&lt;astearns> +1 to disabling on reload (by default)<br>
&lt;fantasai> noamr: also thinking about reloads, reloading from cache, things are not always fast when you reload<br>
&lt;fantasai> noamr: also you probably went from some state to same state<br>
&lt;fantasai> noamr: right now is disable by default, opt in if need arises<br>
&lt;astearns> ack fantasai<br>
&lt;emilio> q+<br>
&lt;khush> +1<br>
&lt;fantasai> fantasai: 100% agree about disaling<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> fantasai: also this is something to think about when designing the at-rule<br>
&lt;fantasai> emilio: Wanted to ask about reloads, or navigating to the same URI<br>
&lt;fantasai> emilio: e.g. if you click to the same URI<br>
&lt;fantasai> noamr: related is history<br>
&lt;fantasai> noamr: I think that navigating to the same URI is also like posting a form, for example<br>
&lt;fantasai> noamr: in which case transitions could be useful?<br>
&lt;fantasai> emilio: I'm fine with special-casing reloads<br>
&lt;fantasai> emilio: but seems like other cases to consider<br>
&lt;dbaron> my intuition is that special-casing reloads makes more sense than special-casing same-uri navigation<br>
&lt;fantasai> emilio: e.g. click on GitHub logo from the GitHub homepage. Seems weird to navigate around<br>
&lt;fantasai> khush: wrt navigation, two types, replacing current entry or adding a new entry<br>
&lt;fantasai> khush: so if you have a link to the same page, retrieve that as a new navigation<br>
&lt;fantasai> khush: but if replacing the current entry, then that shouldn't do a transition<br>
&lt;fantasai> emilio: so are you proposing to do reload, or all replacement navigations?<br>
&lt;fantasai> emilio: I think we all agree that reloads shouldn't trigger VT<br>
&lt;fantasai> emilio: but are there other cases?<br>
&lt;fantasai> emilio: e.g. [lists examples]<br>
&lt;fantasai> emilio: question is what specific concepts to use here, though we all seem to agree on disabling reload by default<br>
&lt;fantasai> noamr: [too quiet]<br>
&lt;fantasai> noamr: might be a good starting point<br>
&lt;fantasai> noamr: redirect, like meta refresh<br>
&lt;vmpstr> q?<br>
&lt;fantasai> noamr: is that also a replace?<br>
&lt;fantasai> noamr: client-side redirects<br>
&lt;fantasai> noamr: are also replace<br>
&lt;fantasai> noamr: [missed]<br>
&lt;emilio> examples: clicking on the same page (not a replaced load), explicit replace load via script, ...<br>
&lt;astearns> ack fantasai<br>
&lt;emilio> fantasai: it seems we all agree on reloads<br>
&lt;emilio> ... but we need more exploration for which other cases shouldn't trigger a transition<br>
&lt;emilio> ... e.g. clicking on a fragment adds to history but probably shouldn't transition<br>
&lt;khush> Unless it's cross-doc, we won't do a transition.<br>
&lt;emilio> ... so should we resolve on reloads not doing transitions and investigating other issues in the issue?<br>
&lt;fantasai> astearns: Proposed resolution is reloads don't trigger VT by default, any objections?<br>
&lt;fantasai> RESOLVED: Reloads don't trigger view transitions by default.<br>
&lt;fantasai> ACTION: Investigate other cases that shouldn't trigger view transitions.<br>
&lt;fantasai> astearns: If we disable a bunch of stuff, re-enabling things might be tricky, so need to be careful when categorizing the set of things<br>
&lt;fantasai> astearns: but let's move on<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8784#issuecomment-1640701514 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:01:14 UTC