On Tue, Aug 12, 2014 at 6:53 PM, Karl Dubost <kdub...@mozilla.com> wrote: > Le 13 août 2014 à 10:09, Jonas Sicking <jo...@sicking.cc> a écrit : >>> And what would be the fallback for non JS user agents (cue accessibility >>> and HTTP scripting here)? >> >> The same as any other time when prerendering is used. The fallback >> would simply be that the next page is loaded at normal speed, rather >> than being prerendered. The only thing that the page would have to do >> special here when the initial page attempts to send a message to the >> prerendered page about which bug's data to load, if the API for >> talking to the message channel is missing, don't do anything. > > <!doctype html> > <html> > <title>bug</title> > <link rel='prerender' > href='http://bugzilla.mozilla.org/show_bug.cgi?justLoadTemplate=1'/> > <a href="/bug0001">my next bug</a> and > <a href="/bug0002">my next next bug</a> > </html> > > In your scenario, this would not work without scripting. I can see how useful > it could be with Firefox OS and transitions between different states of an > application.
Note that the example I used was bugzilla. So this is definitely useful outside of FirefoxOS. But yes, this depends on scripting. It sounds like between the two of us we have three goals * Enable fast navigation between webpages in websites like bugzilla. * When a search result page is loaded, avoid loading and prerendering a separate DOM for each bug. * Avoid relying on JS. I can only think of solutions which fulfill two of those goals at the same time. Which two would be left up to the bugzilla web developers. If you have ideas for how to solve all three at the same time I'm all ears. > I was asking questions about the caching because once > http://bugzilla.mozilla.org/show_bug.cgi?justLoadTemplate=1 > is downloaded, rendered and cached. Note that I don't think anyone is (yet) proposing caching of a prerendered *page*. The individual resources that are loaded to make up the prerendered page will be loaded through the normal http stack, which means that those resources might get cached, or be loaded from cache. But the only thing that's cached is the bytes coming from the network. No parsed datastructures are cached. The parsed and rendered DOM will either be used immediately, or thrown away completely. > It could be reused for all subsequent requests with the same pattern. For now the HTML resource will only be reused for other loads to http://bugzilla.mozilla.org/show_bug.cgi?justLoadTemplate=1. Which likely it mean it will only be used when a page is prerendered. It will not be used if the user simply navigates to a bug page like http://bugzilla.mozilla.org/show_bug.cgi?id=123456 / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
