Bug 57979
| Summary: | Location assignment before onload does not update the current HistoryItem | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mihai Parparita <mihaip> |
| Component: | History | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | beidson, creis, fishd |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Mihai Parparita
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mihai Parparita
*** This bug has been marked as a duplicate of bug 63777 ***