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

I still think that the appropriate place to address this is within the application itself, rather than something in the manifest.

For all of the examples listed, it feels like a developer should be able to design the transition experience based on where the user is navigating from/to - rather than having a single screen that serves as the transition screen. Additionally, developers might want to not have the transition at all for certain navigations - so they would also need some means to enable/disable the transition for certain pages.  

Many transition won't require images at all: without us adding a CSS-like syntax, a transition screen would not allow a developer to control the timing and animation associated with a transition (e.g., "fade out to black over 2 seconds", or "show this image, then remove it by sliding it downwards"). It would mean that each user agent would need to decide how to transition between pages while taking that control away from developers (leading to inconsistencies across browsers). 

I would rather developers be given full control over transitions and they deal with that at the application level. 

-- 
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-240285419