Hi Dave,

it looks like the editor is doing its work via AJAX calls, and Chameleon is probably adding some output to the AJAX page response, that it shouldn't. Chameleon tries to only affect HTML pages but in this case it may be doing the wrong thing.

Can I suggest that you take a look at the AJAX response using your browser's debugging tools, and see what Chameleon is actually adding to the response?

e.g. in Chrome you can right-click on the page and select "Inspect", then click on the "Network" tab and look for the list of additional HTTP requests being generated. Click on one of these and you'll have the option to examine Headers/Preview/Response. The Response is the interesting one here: that should contain some JSON code, and somewhere in that I bet you'll find either a PHP error message or something else added by Chameleon (perhaps debug output?).

So if you can follow that and find it, I should be able to advise on how to get around it.

It is possible that to fix it all you need to do is to include a condition that isolates the page types that you want to add the CSS to. i.e. perhaps the CSS is being added to the AJAX calls. So if it's a JEvents page then we can design a little PHP code to go in the main PHP tab that will ensure that the rule only triggers on the JEvents page load, and not on the AJAX call.

Cheers
Stephen