[Webkit-unassigned] [Bug 57979] New: Location assignment before onload does not update the current HistoryItem

[bugzilla-daemon at webkit.org]

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

           Summary: Location assignment before onload does not update the
                    current HistoryItem
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: History
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mihaip at chromium.org
                CC: beidson at apple.com, fishd at chromium.org,
                    creis at chromium.org


With http://trac.webkit.org/changeset/65340 non-user initiated location updates before onload completes were changed to not create a new HistoryItem. However, they don't update the current HistoryItem with the new URL either, which is inconsistent with both Firefox and the HTML spec (which says "On setting, if the Location object's associated Document object has completely loaded, then the user agent must act as if the assign() method had been called with the new value as its argument. Otherwise, the user agent must act as if the replace() method had been called with the new value as its argument." at http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#the-location-interface).

Test case at http://persistent.info/webkit/test-cases/crbug-78485.html (check the alert that appears).

Originally reported on the Chromium side as http://crbug.com/78485

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