New issue
Advanced search Search tips

Issue 756757 link

Starred by 1 user
Status: Duplicate
Merged: issue 475556
Owner:
yukishiino@chromium.org
Closed: Aug 2017
Cc:
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 651762



Sign in to add a comment

getOwnPropertyDescriptor for 'window' and 'top' of Window interface should not have 'value' and 'writable'

Project Member Reported by tkent@chromium.org, Aug 18 2017 
Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Open DevTools console
(2) Type "Object.getOwnPropertyDescriptor(window, "top")

What is the expected result?
The dump result should not contain 'value' and 'writable'.
Edge and Firefox work so.

What happens instead?
It contains 'value' and 'writable'

Please use labels and text to provide additional information.
http://w3c-test.org/html/dom/interfaces.html contains some sub-tests for this.

Comment 1 by adithyas@chromium.org, Aug 18 2017

Owner: yukishiino@chromium.org
Status: Assigned (was: Untriaged)
I think a few Window properties like "top" are being marked as data_attributes instead of accessors, yukishiino@ could you take a look?

Comment 2 by yukishiino@chromium.org, Aug 21 2017

Mergedinto: 475556
Status: Duplicate (was: Assigned)
Yeah, cross-origin accessible IDL attributes on Window are wrongly data properties.  Once we fix LAP-context issue and implement the Incumbent realm, then I think that we should be able to get rid of this data property hack.
►

Sign in to add a comment