Re: [w3ctag/design-reviews] Disabling UA transitions for same-document navigations (Issue #835)

> Can you give a bit more context on why these are 2 separate review requests?

Sure. We found 2 separate problems with choosing between a default transition designed by the UA vs a custom transition designed by the author:

- There are some cases where the browser UX is such that it's not possible for the site to customize the transition. Imagine a film strip type visualization of the navigation history. For these cases, the UA transition always wins and we just need a hook to inform the site of this choice. #834 handles that.

- There are some cases where if the author designs a transition, it should be given preference over the default UA transition. Easiest example would be clicking the back button on a desktop browser. It makes sense for the custom transition on the site to win instead of overriding it with a UA transition. But there's currently no way for the site to indicate to the browser that it has designed a custom transition for a navigation. Such use-cases needs a different API (which this issue is about).

That said, I heard similar feedback against disabling any existing browser UX (like transitions on swipe gestures) that users are accustomed to at HTML WG. So this proposal needs more refinement. I can close it for now and reopen with more details. Does that sound reasonable?

Until there is a proposal here, browsers will have to be conservative about which cases have a UA transition (which overrides a site's custom transition). Since #834 will let sites detect these cases, it will be sufficient to not cause breakage because of "double transitions".

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/835#issuecomment-1638874530
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/835/1638874530@github.com>