On Sun, Aug 2, 2009 at 1:48 PM, <[email protected]> wrote: > (Yes, we probably should not put all this into cajita.js, but > that's not the issue at the moment.) >
Still absorbing the rest. While I agree that this inclusion is not the present issue, I can't help but comment ;). cajita.js has not been and should not become dependent on the browser as a hosting context. It should be just as applicable to using Caja on the server side. This is part of the rationale for the cajita vs domita separation. References to "window", "document", and <script> tag manipulation within cajita.js are not legit. Since your code does not seem to depend on "window" actually being a window object, but rather only on it being the global object, you should refer to "global" which has already been brought into scope there for exactly this purpose. -- Cheers, --MarkM
