80697 2012-03-09 04:37:02 -0800 Broken behavior for back-button after history.pushState() + location.replace() 2020-06-19 11:01:46 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified UNCONFIRMED InRadar P2 Major --- 0 shogun70 webkit-unassigned aroben beidson bugzilla fishd josh shogun70 timdream webkit-bug-importer oldest_to_newest 574811 0 shogun70 2012-03-09 04:37:02 -0800 To reproduce: 1. Navigate to http://www.webkit.org/ 2. Open the Javascript console and enter the following history.pushState({}, null, "/blog/"); The address-bar now says http://www.webkit.org/blog/, but the page hasn't changed (expected behavior). 3. Now enter the following location.replace("/blog/"); The address-bar now says http://www.webkit.org/blog/, and the page reflects this. 4. Press the back-button. The address-bar now says http://www.webkit.org/, but the page hasn't changed from the "/blog/" contents. This behavior is also observed in up-to-date Chrome. 575488 1 shogun70 2012-03-10 02:38:25 -0800 The same broken behavior is also exhibited if step 3 is: location.reload() 607151 2 shogun70 2012-04-20 23:04:09 -0700 A work-around for this issue is to replace step #3 with: history.replaceState({}, null, currentURL); location.replace(nextURL); where currentURL = "http://www.webkit.org/" or "/" nextURL = "/blog/" for the demo given above. This work-around can cause a flash of the currentURL in the address bar, and it seems bizarre that this should work while the straight-forward code path fails. 607336 3 shogun70 2012-04-22 05:26:09 -0700 An almost satisfactory work-around for this issue is to replace step #3 with: history.replaceState({}, null, "#"); location.replace(""); I guess this indicates that identified bug is only an issue when `location.replace(url)` is the precise equivalent of `location.reload()` (and there has been a previous invocation of `history.pushState`.) 982349 4 aroben 2014-02-19 07:48:26 -0800 *** Bug 93506 has been marked as a duplicate of this bug. *** 982350 5 aroben 2014-02-19 07:49:57 -0800 See https://bugs.webkit.org/show_bug.cgi?id=93506 for a live test case. AFAICT this behavior disagrees with the spec and with Firefox. 1664423 6 webkit-bug-importer 2020-06-19 11:01:46 -0700 <rdar://problem/64537409>