Status: New
Owner: ----
CC: erights
Labels: Type-Enhancement Priority-Low Component-SES Usability
New issue 1875 by [email protected]: Look into using “source maps” for SES
rewrite
http://code.google.com/p/google-caja/issues/detail?id=1875
Outside of interactive debugging, stack traces from SES guest code are
useless, because they have no filename (coming from eval) and mismatched
line numbers (due to mitigateSrcGotchas).
We may be able to fix one or both of these by using the “source maps”
feature in browsers, which is intended to translate line numbers in
rewritten code back to the original source file. Investigate this.
--
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.
