dcheng 96eda1f7d1 Fix receiver checks for v8::Function on a remote context receiver. ... v8 allows the embedder to specify a global template to use when creating a new context. However, v8 does not use the supplied template directly when creating the global proxy: it creates a unique template for each global proxy. However, this is problematic for remote contexts: functions cannot use strict receiver checks with the remote context, as the global template will never match the global proxy. To fix this, remote contexts now also include a remote global object in the prototype chain that is instantiated with the global template. This mirrors the way the global proxy is configured for a full v8 context, and allows strict receiver checks to work. BUG=527190 Review-Url: https://codereview.chromium.org/2677653002 Cr-Commit-Position: refs/heads/master@{#43361}		2017-02-22 10:13:24 +00:00
..
access-check-unittest.cc	Always early return from HandleApiCallHelper on access check failure.	2017-02-20 10:07:05 +00:00
exception-unittest.cc	Clear pending message during Isolate::CancelScheduledExceptionFromTryCatch.	2017-02-08 16:12:59 +00:00
isolate-unittest.cc	Remove a few unnecssary scopers from unit tests.	2017-02-17 09:51:07 +00:00
remote-object-unittest.cc	Fix receiver checks for v8::Function on a remote context receiver.	2017-02-22 10:13:24 +00:00
v8-object-unittest.cc	Remove a few unnecssary scopers from unit tests.	2017-02-17 09:51:07 +00:00