[Webkit-unassigned] [Bug 93506] New: History state is incorrect attached to new document when loaded via location.assign or location.replace

[bugzilla-daemon at webkit.org]

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

           Summary: History state is incorrect attached to new document
                    when loaded via location.assign or location.replace
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: History
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: josh at joshpeek.com
                CC: aroben at webkit.org


Created an attachment (id=157271)
 --> (https://bugs.webkit.org/attachment.cgi?id=157271&action=review)
Layout test cases

To reproduce, load an initial document, then call history.pushState({foo:true}, "", url) to set a new url. Calling location.assign or location.replace with the new current url will correctly reload a new document. But the history state associated with the document is incorrect. `event.state` will be `{foo:true}` instead of `null` and pushing the back button will cause a pop state event instead of loading the previous document.

    # URL: /
    history.pushState({foo:true}, "", "/other.html")
    location.assign("/other.html")

    # URL: /other.html
    event.state # => {foo:true} should be null
    history.back() # => causes popstate instead of loading "/"

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