From 44da6795888d90cc7d4181a57e5b7aeafe461fb5 Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Tue, 27 Nov 2018 15:13:42 +0100 Subject: [PATCH] WindowProxy and Location use ordinary internal methods by default Fixes #4189. --- source | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source b/source index b183fe20590..5af18751cc0 100644 --- a/source +++ b/source @@ -79104,15 +79104,15 @@ interface BarProp { Window object wrapped by the browsing context's associated WindowProxy object is changed.

+

The WindowProxy exotic object must use the ordinary internal methods except where + it is explicitly specified otherwise below.

+

There is no WindowProxy interface object.

Every WindowProxy object has a [[Window]] internal slot representing the wrapped Window object.

-

The WindowProxy object internal methods are described in the subsections - below.

-

Although WindowProxy is named as a "proxy", it does not do polymorphic dispatch on its target's internal methods as a real proxy would, due to a desire to reuse machinery between WindowProxy and Location objects. As long as the @@ -81673,10 +81673,10 @@ interface Location { // but see also As explained earlier, the Location exotic object - requires additional logic beyond IDL for security purposes. The internal slot and internal methods - Location objects must implement are defined below.

+ requires additional logic beyond IDL for security purposes. The Location object must + use the ordinary internal methods except where it is explicitly specified otherwise below.

-

Every Location object has a [[DefaultProperties]] internal slot +

Also, every Location object has a [[DefaultProperties]] internal slot representing its own properties at time of its creation.

[[GetPrototypeOf]] ( )