17598 2008-02-28 16:51:28 -0800 FrameLoader should treat all location changes during onload as redirects 2010-07-31 15:08:17 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) PC All RESOLVED DUPLICATE 42861 P2 Normal --- 1 pkasting webkit-unassigned abarth grahamperrin mihaip sam oldest_to_newest 72311 0 pkasting 2008-02-28 16:51:28 -0800 Currently the FrameLoader treats some types of location changes as redirects: meta refresh 0, setting document.location.href (I think this is treated as a redirect at any time, though perhaps it should only be treated as such before/during onload). Other cases can fall through the cracks, however. For example, a page that has an onload handler that does a form.submit with a form action that's a different URL to load should be treated as a client redirect, but is not. I think any location change before/during onload should be treated as a redirect, but the example above is the only concrete case where I know this doesn't happen; maybe there are others. 72312 1 beidson 2008-02-28 17:21:23 -0800 Interesting. Wonder how hard it would be to concoct a series of tests to demonstrate Firefox and even IE's behavior, to compare against WebKit 219106 2 pkasting 2010-04-29 11:18:50 -0700 abarth has been doing some work on FrameLoader. 258639 3 mihaip 2010-07-31 15:08:17 -0700 I've been working on implementing this for my fix for bug 42861. The bug comments have test cases that compare Chrome, Safari, Firefox and IE's behavior in a bunch of scenarios, but briefly, changes to window.location.href up until the onload handler finishes running shouldn't generate a session history entry, but programmatic form submits should (if we want to be consistent with other browsers, the HTML 5 spec is silent on this matter). *** This bug has been marked as a duplicate of bug 42861 ***