Re: [w3ctag/design-reviews] Incubation: seamless page transition with deferred commit (Issue #1177)

noamr left a comment (w3ctag/design-reviews#1177)

> [@noamr](https://github.com/noamr) Thanks for updating the explainer. We had a look again at our TAG F2F. There is still malformed markdown around "Possible usage:" in the code block for solution 1 - please could you fix that?

Fixed

> 
> What user or developer research has been carried out to determine which transitions are most important to support? It's important to address the end user needs - even if only briefly - at the very start of the explainer. Please could you mention these? It's OK to quickly follow up with the developer needs that follow from those end user needs.

Done

> 
> Generally, we believe this proposal introduces significant complexity while not covering all transition effects (e.g., cross-fades), and it seems that this adds a dependency on prerendering. What do you think?
> 
> We see there are two solutions in the explainer. We would prefer a simpler, declarative API that covers most use cases first, before giving authors the ability to handle more advanced use cases with the imperative API.

Thanks, I've updated the explainer with some more details behind the declarative alternative. We did find that the imperative approach, though might be necessary for some use cases, is a bit footgunny as it requires cleaning up the state in case of BFCache restore.

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

Message ID: <w3ctag/design-reviews/issues/1177/4168498889@github.com>