Re: [w3c/manifest] Add optional Transition Screen member (#478)

I'm into fixing the problem mentioned in the OP, but I agree that the manifest isn't a great place to solve it.

With service worker, you get near-instant navigations, even if the body content is coming from the network. Check out jakearchibald.com in the latest Chrome - the header of the page is stored locally, but the rest streams from the network.

What this doesn't give us is a nice transition between states, and it bugs me that developers end up reimplementing the whole navigation system just for transitions.

I'd love for us to look at navigation transitions again, using http://cwiiis.github.io/gaia-navigator/ as a starting point (I haven't dug into the proposal too much, so it might be perfect as it is). 

@RobDolinMS @seksenov if we were to try and get a cross-browser group together to think about this, who should I keep in the loop at MS?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/478#issuecomment-247547917