[Webkit-unassigned] [Bug 42861] Session history should skip over JS redirects

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 23 14:03:49 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=42861





--- Comment #3 from Mihai Parparita <mihaip at chromium.org>  2010-07-23 14:03:49 PST ---
Here's some more systematic test cases:

persistent.info/webkit/test-cases/redirects/fragment.html?<timeout>
persistent.info/webkit/test-cases/redirects/page.html?<timeout>

Where <timeout> is the timeout in milliseconds before navigating to the destination (by setting window.location). In the case of fragment.html that's #foo, in the case of page.html that's destination.html. If the timeout param 0, the navigation is done onload (with no setTimeout call). 

The test was to visit google.com, then the page, wait for the redirect to complete, and press back. A result of "g.com" means that google.com was shown, while "page" means that the interstitial page was shown.

          Chrome     WebKit  Firefox  IE 8
fragment  
  onload  g.com      page    g.com    g.com
  200ms   g.com      page    page     g.com
  1000ms  g.com      page    page     g.com
  5000ms  g.com      page    page     g.com
  6000ms  page       page    page     g.com
page
  onload  g.com      page    g.com    page
  200ms   g.com      page    page     page
  1000ms  g.com      page    page     page
  5000ms  page       page    page     page
  6000ms  page       page    page     page

Observations:
- No browser other than Chrome has time-dependent behavior.
- All browsers (except for IE 8) handle fragment and page navigation the same
- There is precedent for modifying WebKit to replace (session) history entries for JS redirects during onload.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list