Re: [w3ctag/design-reviews] View Transitions API (Issue #748)

We looked at this again today and had some questions:
- Is the current experimental implementation in Chrome up to date with the current syntax? 
- Do you have feedback from authors that have used the experimental implementation? Have you observed any of them using it and seen what they struggle with? 

We are particularly concerned about the complexity and ergonomics of this API, and we (TAG members) have not yet had the a-ha moment where we fully understand how all the pieces come together to create a transition in a real use case from scratch. Given the trouble we've had with it, that gives us some pause about DX in the wild. Perhaps it's an inherently complicated problem and there cannot possibly be a simpler solution, but it is a concern that came up several times in our discussions.

@jakearchibald

Regarding https://github.com/w3ctag/design-reviews/issues/748#issuecomment-1225922770 , with the current API, `updateTheDomSomehow()` needs to be repeated twice, which is fine when it's a separate function, but it means all such DOM modifications need to become separate functions, which as an author I'd find annoying.

Re:frameworks, I’m sure it's *possible*, and yes it doesn't look too bad, but it's unfortunate that it requires people to find out implementation details like `nextTick()` that don't come up during typical framework usage, and are different per framework. I think the current callback API is less friendly to the multiple layers of abstraction in modern web apps. It's not the end of the world if it doesn't change, but I still think not having a callback would serve the majority of cases better. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/748#issuecomment-1317356128

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/748/1317356128@github.com>