New issue
Advanced search Search tips

Issue 683013 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

executing{Window,Frame} is actually relevantRealm{Window,Frame}

Project Member Reported by kouhei@chromium.org, Jan 20 2017

Issue description

The method name executingWindow suggests that this refers to "Current Realm", but the impl actually refers to "Relavant Realm".

1. Rename the methods to match the impl.
2. Fix all the misuses.
 

Comment 1 by cvrebert@google.com, Jan 20 2017

Summary: executing{Window,Frame} is actually relevantRealm{Window,Frame} (was: executing{Window,Frame} is actually relavantRealm{Window,Frame})
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.
Status: Available (was: Unconfirmed)
My understanding is that the root problem is that:
DOMWindow is NOT an ExecutingContext, but Document is an ExecutingContext, while WorkerOrWorkletGlobalScope (a counterpart of DOMWindow) is an ExecutingContext.

So, the right fix should be to make DOMWindow inherit from ExecutingContext rather than renaming.

Project Member

Comment 5 by sheriffbot@chromium.org, May 9 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Comment 7 by kouhei@chromium.org, May 10 2018

Please talk to yukishiino@ before tackling this.
Cc: kouhei@chromium.org
Owner: yukishiino@chromium.org
Status: Assigned (was: Available)

Sign in to add a comment