[Webkit-unassigned] [Bug 171567] New: window.customElements should be associated with each Window

[bugzilla-daemon at webkit.org]

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

            Bug ID: 171567
           Summary: window.customElements should be associated with each
                    Window
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML DOM
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: d at domenic.me
                CC: cdumez at apple.com

Currently it appears to not be, in three ways:

- It gets cleared (set to undefined) when an iframe is removed from the DOM
- It gets reset to a new value on navigation from the initial about:blank, even though the Window stays the same during such a navigation
- It does not get cleared during document.open(). Per spec this is supposed to create a new Window; non-Firefox browsers do not follow this, but they do generally clear Window-associated stuff, and so we should do the same for window.customElements.

Tests at http://w3c-test.org/custom-elements/custom-element-registry/per-global.html

-- 
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/20170502/1d3dcaed/attachment.html>