This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21970 - Window.opener probably needs to be visible cross-origin
Summary: Window.opener probably needs to be visible cross-origin
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-08 17:25 UTC by Bobby Holley (:bholley)
Modified: 2013-06-14 18:28 UTC (History)
3 users (show)

See Also:

Attachments

Description Bobby Holley (:bholley) 2013-05-08 17:25:32 UTC 
See the chart at [1]. It looks like |opener| is the one property that all UAs support cross-origin but the spec doesn't.

[1] https://bug839867.bugzilla.mozilla.org/attachment.cgi?id=712247
Comment 1 Ian 'Hixie' Hickson 2013-06-07 22:53:53 UTC 
How about blur(), close(), focus(), and .closed?
Comment 2 contributor 2013-06-07 22:55:52 UTC 
Checked in as WHATWG revision r7941.
Check-in comment: Example window.opener cross-origin.
http://html5.org/tools/web-apps-tracker?from=7940&to=7941
Comment 3 Bobby Holley (:bholley) 2013-06-08 00:19:52 UTC 
(In reply to comment #1)
> How about blur(), close(), focus(), and .closed?

Oh yeah. Missed those.
Comment 4 contributor 2013-06-14 18:28:51 UTC 
Checked in as WHATWG revision r7977.
Check-in comment: Define window.close; update the list of members exposed cross-origin on Window to match reality
http://html5.org/tools/web-apps-tracker?from=7976&to=7977