[Webkit-unassigned] [Bug 235893] Accessing `window.frameElement` should not report error if parent is cross-origin

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jan 31 09:53:41 PST 2022


Sam Sneddon [:gsnedders] <gsnedders at apple.com> changed:

           What    |Removed                     |Added
                 CC|                            |cdumez at apple.com

--- Comment #1 from Sam Sneddon [:gsnedders] <gsnedders at apple.com> ---
Note this is only a message in the console; window.frameElement does return null in the cross-origin case as far as I can tell.

There's nothing standardised about what does and doesn't get put in the console (as errors, warnings, or in any other form). I _believe_ (but I'm not totally sure!) that the current WebKit behaviour is to log in the console for any blocked cross-origin access. Do you think that logging when no exception is thrown is confusing, or that logging an error when no exception is thrown is confusing?

(http://wpt.live/html/browsers/windows/nested-browsing-contexts/frameElement.sub.html covers this case, and we indeed pass all the tests.)

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/20220131/0eb8f269/attachment.htm>

More information about the webkit-unassigned mailing list