Status: Accepted
Owner: kpreid.switchb.org
Labels: Type-Enhancement Priority-Low
New issue 1751 by kpreid.switchb.org: Provide 'console' as part of default
environment
http://code.google.com/p/google-caja/issues/detail?id=1751
Modern browsers, AFAIK, provide a 'console' object unconditionally as part
of the global environment. We should do the same, so that code written
assuming it does not fail, and to start providing better debugging tools.
Issues:
- How much of the console interface should we expose? Are there security
risks from passing bare objects to it?
- The console provided by e.g. firebug, at least historically, is somewhat
less than first class and we may need to create specialized wrappers (see
the current one in browser-test-case.js).
- It should be possible for the host page to filter/redirect the logging,
or at least to (a) turn it off or (b) specify a prefix for all messages.
cajaVM.log should be deprecated in favor of console to reduce Caja/browser
API differences. (startSES.js comments implies that cajaVM.log is to be
deprecated in favor of ses.logger being exposed in some way; look into what
the thinking was there.)
See also issue 1720 (console and other interfaces on the playground).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
