commit 094023a4b125962fd809c36bad3fbb088382507d
author Peter Kotwicz <pkotwicz@chromium.org> Sat Oct 20 04:40:08 2018
committer Commit Bot <commit-bot@chromium.org> Sat Oct 20 04:40:08 2018
tree 416e66c71529f3548b0778dc140266837ffb6ff7
parent 57df06767601e98a1b51239d3a5f3862e3d000dd

[Android WebAPK] Preserve history state when relaunching WebAPK

This CL reverts https://crbug.com/307333 for WebAPKs but not webapps.
That CL made webapps reload when a user:
- navigated back to a webapp via Android Recents
AND
- the webapp had been killed (which means that it is likely that a
  long time elapsed since the webapp was launched has passed)

A WebAPK user is using window.history.pushState() to cache that a web page
was reached by launching a WebAPK instead of by navigating on the web.
The behaviour introduced in https://crbug.com/307333 was preventing the
history state from getting restored when the user navigates back to the
WebAPK via Android recents and Chrome has been killed.

The rationale for reverting the behaviour for WebAPKs but not webapps is
that WebAPKs are supposed to be sophisticated apps. Reloading the page
takes control away from web developers.

BUG=888100

Change-Id: Icb4803b0ee8b3444e0aade2acc2473b8ce1c23b7
Reviewed-on: https://chromium-review.googlesource.com/c/1275290
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601405}