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

I'm not sure we need this, as we already have in the platform:

```HTML
<link rel="prerender" href="nextpage.html">
<!-- or dynamically adding the above with JS! -->
```

This allows for instantaneous pre-rendering of web pages when there is clear intent that the user is going to navigate. It also handles correctly sizing the next navigation, which wouldn't be possible with an image. Additionally, it is much more size and memory efficient than using an image, as the browser is in full control of the pre-render process (and no additional resources need to be downloaded, the existing css, and assets can be used, etc.). 

Additionally, using pre-render together with the Cache API results in lightning fast navigations. But even without pre-render, the Cache API already makes it possible to cache next pages in a very efficient manner (we are talking >100ms render times, as all resources are already available), thus transitions shouldn't be needed. 

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