Comment #1 on issue 1766 by [email protected]: Google Visualization taming
URL rewriter fails
http://code.google.com/p/google-caja/issues/detail?id=1766
Kibitzing:
I'd like to see a move towards having a more explicit public/host-side API,
so as to have more formal definition of what is safe for users of Caja to
make use of, and so that membrane-breaking bugs are less likely. Therefore,
I would rather see a solution which has two different rewriteUri functions,
than one which jumps through hoops to use it two ways or to make it usable
two ways.
Also, I think that the implementation of rewriteUri should probably not
live in Domado as it currently does; I think there's some unnecessary
indirection as a result, and there's no particular reason to refuse to work
with URIs in a context which has no HTML DOM.
--
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.
