Le 13 août 2014 à 09:13, Jonas Sicking <jo...@sicking.cc> a écrit : > The goal of prerender is to improve performance when navigating to a > new page.
my understanding too. > I'm talking about doing a full rendering of a "template page". I.e. a > normal webpage which the website can then use JavaScript to mutate > into the page that the user wanted to navigate to. [cut the explanation] So I guess I'm getting confused by the term 'prerender' and the scope. It looks like indeed more like a single page app (with all the caveats of client side generated pages) or a rel='template' more than a rel='prerender'. What would be the markup for the scenario you are explaining? And what would be the fallback for non JS user agents (cue accessibility and HTTP scripting here)? If I do <link rel='prerender' href='http://example.org/nextbug0001.html'/> How the server knows it has to send the template or the full HTML page? What is the HTTP caching story with regards to this URI http://example.org/nextbug0001.html? And how does it help with http://example.org/nextbug0002.html in terms of caching? -- Karl Dubost, Mozilla http://www.la-grange.net/karl/moz _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
