[Webkit-unassigned] [Bug 133531] REGRESSION: Can't change the prototype of the lexical global object (changes the proxy prototype instead)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=133531





--- Comment #3 from Jay Freeman (saurik) <saurik at saurik.com>  2014-06-06 00:47:05 PST ---
I guess a different question I could be asking: how am I able to get an actual legitimate reference to the global object, at the JavaScriptCore API level, if JSContextGetGlobalObject returns a JSProxy? It at least used to be the case that I could, even in the context of WebKit, call JSContextGetGlobalObject on the JSGlobalContextRef for a WebFrame (retrieved from a web page being rendered in a view), modify its prototype using JSObjectSetPrototype, and then have my extended features available to the executing JavaScript context. Why is JSContextGetGlobalObject, not code running "this" but the low-level C API, returning a proxy rather than the actual global object? :(

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.