Early page scripts are sometimes not injected after fast back/forward navigations via WKBackForwardListItems. |
||||||||||||||
Issue descriptionWe've seen this occur when navigating a WKWebView via its WKBackForwardList to pages created or affected by pushState() and replaceState(); an Apple radar will be filed for this issue.
,
Oct 27 2016
This happens flakily in non-test environments. It seems to happen for fast back/forward BFLI navigations when a page hasn't finished loading yet. I tried to reproduce in a test app for a radar, but it doesn't seem to be happening. Maybe this is due to the size and complexity of our early injection script? Or it might be that the script is failing somehow before our window.history overrides are injected. Sample app is attached.
,
Oct 27 2016
If we can not reproduce this with test app, then perhaps the bug is not in WKWebView, but it Chrome. Kurt, please revisit this bug, once synchronous pushState/replaceState is implemented.
,
May 30 2017
,
Jun 1 2017
,
Jul 11 2017
Kurt or Mohammad, could you please file radar for this bug.
,
Nov 30 2017
,
Sep 14
,
Oct 17
We found the root cause. For fast back forward navigations the page is retrieved from the cache and scripts are already present on the page. This can be closed after Legacy navigation code removal.
,
Oct 26
,
Oct 26
,
Oct 26
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by kkhorimoto@chromium.org
, Oct 26 2016