Hi. Thanks. I just tried es5Mode: true
and I got Uncaught TypeError: undefined is not a function caja.js:247<http://caja.appspot.com/caja.js> It seems that this was caused the lack of an onFailure function in . function initialize(config /*, opt_onSuccess, opt_onFailure */) { which is called with only one argument. The err variable contained "ES5 mode requested but browser is unsupported". I'm using Chrome Version 33.0.1750.146 m When I removed es5Mode entirely I get Uncaught Error: SES not supported, aborting taming frame initialization. ses-single-frame.js?debug=1:9316<https://caja.appspot.com/5643/ses-single-frame.js?debug=1> XMLHttpRequest cannot load https://caja.appspot.com/cajole?url=http%3A%2F%2Ftoontalk.appspot.com%2Find…&emit-html-in-js=true&renderer=pretty&input-mime-type=text%2Fhtml&alt=json<https://caja.appspot.com/cajole?url=http%3A%2F%2Ftoontalk.appspot.com%2Findex.html&build-version=5643&directive=ES53&emit-html-in-js=true&renderer=pretty&input-mime-type=text%2Fhtml&alt=json>. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. 1. caja.js:247 <http://caja.appspot.com/caja.js> By the way, the only reason I added es5Mode: false was advice from https://groups.google.com/forum/#!topic/google-caja-discuss/38tIX-EKEn8 but I guess that is a year old now. I thought it was a way to avoid the 'Uncaught Error: SES not supported, aborting taming frame initialization' error. So I tried to use the sample guest page from https://developers.google.com/caja/docs/gettingstarted/ (http://toontalk.appspot.com/guest.html) instead of my own. And I still get these errors with es5Mode: true but it does work when I use false or don't specify it But when I don't specify es5Mode while it works the Chrome dev tools console shows: 1. Uncaught Error: SES not supported, aborting taming frame initialization. ses-single-frame.js?debug=1:9316<https://caja.appspot.com/5643/ses-single-frame.js?debug=1> Unable to use SES. Switching to ES53. By the way the Caja Playground offers 'ES5 Mode (Experimental)' and ES3/5 (which led to '500 The call failed on the server; see server log for details'). But with ES5 the Compiler and Runtime message tabs are empty. And it partly renders. Thanks again for your help On Monday, March 17, 2014 9:36:06 PM UTC, Kevin Reid wrote: > > On Sat, Mar 15, 2014 at 10:35 AM, Ken Kahn <[email protected]<javascript:> > > wrote: > >> I don't understand what to do about this error >> >> XMLHttpRequest cannot load >> https://caja.appspot.com/cajole?url=http%3A%2F%2Ftoontalk.appspot.com%2Find…&emit-html-in-js=true&renderer=pretty&input-mime-type=text%2Fhtml&alt=json<https://caja.appspot.com/cajole?url=http%3A%2F%2Ftoontalk.appspot.com%2Findex.html&build-version=5643&directive=ES53&emit-html-in-js=true&renderer=pretty&input-mime-type=text%2Fhtml&alt=json>. >> >> No 'Access-Control-Allow-Origin' header is present on the requested >> resource. Origin 'null' is therefore not allowed access. >> > > Your host page is trying to contact the server to get rewritten content, > but fails because it's not at the same domain. (We should put the mentioned > header on caja.appspot.com, but haven't.) > > >> Caused when loading the following: >> ... >> es5Mode: false, >> > > By specifying es5Mode: false, you have required the use of the server-side > rewriter (aka ES5/3 mode), thus resulting in the above error. To avoid it > you would need to run your own server on the same domain. > > However, ES5/3 is deprecated. Please specify "es5Mode: true" to test > against the client-side-only mode, which will become the only mode in the > future. > -- --- 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/d/optout.
