NoStatePrefetch does not work for Instant Search. |
|||
Issue descriptionThe steps for instant prerender are: 1) create a prerender contents for the base search engine URL 2) navigate the prererender to the actual query With NoStatePrefetch, only 1) is done (which still has some benefits). It is also not clear wether doing NoStatePrefetch with the actual query would be very useful or not, so maybe this is WAI. In any case, this explains why the Prerender.Instant_PrefetchTTFCP.Warm.Cacheable.Visible barely has any counts for NoStatePrefetch.
,
Mar 15 2017
we could make a prefetch for their XHR right? Then we could make sure that the XHR will be exactly the same when the actual SRP asks for the same query. Brittle though, but may discuss with Search. I still don't understand why the counts are low, but non-zero. Are the counts coming from cases when users accidentally type the exact URL that we feed the NoStatePrefetch with (the one without the search query)? How does the URL look like? Or maybe the (2) happens if some race conditions align?
,
May 16 2017
,
Aug 16 2017
we had a proposal to cover some of the instant prerender usecases (http://go/chrome-instant-without-prerender - sorry, googlers only), but the coverage seemed small. |
|||
►
Sign in to add a comment |
|||
Comment 1 by mattcary@chromium.org
, Mar 13 2017