New issue
Advanced search Search tips

Issue 658706 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Global proxy objects should proxy Object::GetInternalField(index) to the underlying global object.

Project Member Reported by yukishiino@chromium.org, Oct 24 2016

Issue description

When V8 called back DOM operations of global objects in Blink, v8::FunctionCallbackInfo::Holder() points to the global proxy object, not the global object.  There is no way to determine if Holder() is the global proxy object or global object, so it's difficult to extract an internal field from the global object.

We'd like the global proxy object to proxy the call to GetInternalField(index) to the underlying global object so that Holder()->GetInternalField(index) works even when Holder() is the global proxy object.

 
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
Owner: jochen@chromium.org
Reassigning to jochen who's working on this.
Cc: haraken@chromium.org dcheng@chromium.org
Now that the global proxy also has internal fields, you can just use them, no?
Status: WontFix (was: Assigned)
Yes, this is what the latest version of the CL does.

Sign in to add a comment