[Webkit-unassigned] [Bug 196990] New: Parent window's `history.state` is set to `null` when `history.pushState` is called by a child iframe

[bugzilla-daemon at webkit.org]

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

            Bug ID: 196990
           Summary: Parent window's `history.state` is set to `null` when
                    `history.pushState` is called by a child iframe
           Product: WebKit
           Version: Safari 12
          Hardware: Macintosh
                OS: macOS 10.14
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: History
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: contact at atticuswhite.com

Created attachment 367579

  --> https://bugs.webkit.org/attachment.cgi?id=367579&action=review

Reproducible script that can be ran on bugs.webkit.org

What happened:
When an `iframe` calls `window.history.pushState`, the parent window's `window.history.state` becomes replaced with a `null` value.


Expected behavior:
The top page's `history.state` should remain untouched.


Steps to reproduce:
1. Give the top page a `history.state` value (eg, call `window.history.pushState({something}, 'something')`)
2. In an iframe, perform `window.history.pushState(...)`
3. In the top page, observe that `history.state` has become set to `null`

Attached is a minimal working example of the problem that can be ran in the JS console on `bugs.webkit.org`

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190416/30bd6502/attachment-0001.html>