On 2015/07/11 at 17:09:02, caitpotter88 wrote:
On 2015/07/10 17:24:39, adamk wrote:
> Just to link discussions together further, the spec-world discussion
about
this
> is taking place at:
>
>
https://lists.w3.org/Archives/Public/public-script-coord/2015JulSep/0022.html
Per the discussion in the etherpad, the best thing to do is probably just
to
install [Unforgeable] + readonly @@toStringTag/@@isConcatSpreadable/etc
attributes on cross-origin objects, and ignore the security check.
Preferred? Not preferred?
My reading of the etherpad doesn't match this interpretation. In the current
Blink implementation, an [Unforgeable] attribute will have the same value
to all
observers (not just cross-origin accesses). The draft "spec" in the etherpad
suggests that each access to a frame from another origin generates a new
Window
object.
https://codereview.chromium.org/1230793002/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
