Charles Kendrick wrote:
On Fri, Jun 8, 2012 at 6:48 PM, Erik Arvidsson<erik.arvids...@gmail.com> wrote:
On Fri, Jun 8, 2012 at 4:10 PM, Charles Kendrick<char...@isomorphic.com> wrote:
Once again, exposing the actual arguments, receiver and function
object references is a security issue and completely out of scope for
this. This is not related to cross domain access but related to object
capabilities.
Erik how do you reconcile this with the fact that this information can
already be obtained in most production browsers via stack walking?
Stack walking is not available in strict functions.
Interesting, but it doesn't speak against programmatic access to the
call stack.
But you wrote "how do you reconcile" and Erik answered. We do not want a
non-debugger API that works only some of the time. Debuggers, in
contrast, must be able to pierce the veil of "use strict".
Erik's proposal is for the string-valued .stack property.
A debugger API is further off from standardization. Mozilla has a new one:
Video: http://www.youtube.com/watch?v=WKIkOcuVG7w
https://wiki.mozilla.org/JSInspector
https://wiki.mozilla.org/Remote_Debugging_Protocol
https://wiki.mozilla.org/DevTools/Features/Debugger/Notes
This is in Firefox Nightlies now.
/be
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
