New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599500 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Allow to request Prerendering for saving WebContents to MHTML for offline use

Project Member Reported by gabadie@chromium.org, Mar 31 2016

Issue description

$title
 

Comment 2 by pasko@chromium.org, Apr 4 2016

Labels: -Pri-3 Pri-2
Summary: Allow to request Prerendering for saving WebContents to MHTML for offline use (was: Tune prerender for offlining use.)
Important things to consider:
* When in foreground, the offlining prerender should not compete with other prerenders
* It would be nice to get offlining prerenders killed as soon as Chrome is foregrounded, this should be the responsibility of the caller, I think
* On low end devices the offlining prerender should be allowed, but it should not spawn new renderers if one background renderer process (from a tab) is already alive

Comment 3 by pasko@chromium.org, Apr 4 2016

Cc: talo@chromium.org dim...@chromium.org
talo, dimich, dougarnett: Under Settings->Privacy there is "Use prediction service to load pages more quickly". We normally get prerenders disabled if the user chooses to opt out there.

If I understand correctly, we want to ignore this setting when background offliner asks the PrerenderManager to AddPrerenderForOffline().
Yes, that would be my take too. I think we would want to make a policy decision at higher level on whether to do prerenders for an user-directed async load request vs. maybe not for speculative requests.
+1, our first feature using the prerenderer will be Async Loading which will be a very explicit user action every time, and not a speed optimization, so this check is not directly applicable.
Project Member

Comment 6 by bugdroid1@chromium.org, Apr 28 2016

Comment 7 by pasko@chromium.org, Jul 28 2016

Owner: pasko@chromium.org
Status: Assigned (was: Started)

Comment 8 by pasko@chromium.org, Jul 28 2016

Status: Fixed (was: Assigned)

Sign in to add a comment