Problem with CB Google Translate

It's not CB or anything related to CB that's erroring it's Google's own JavaScript loaded in from Google that is. Regarding what's causing it I don't know. If you modified beez3 template try downloading a fresh Joomla 3 package from Joomla.org and comparing the files and reverting some of your modifications.

That's what I'll do, I'll let you know! thank you

Good morning!
I just partially solved the problem. I have already started by deactivating / activating each plugin, one by one, without conclusive result. I then looked in the Firefox developer command for all the error messages and looked at each message one by one. I found, after multitudes of google searches, that some webmasters had problems displaying Google ads because of what is called MooTools. So I installed DJQueryMonster (plugin to disable MooTools) and obviously the Google translation works again. On the other hand, I manage to have the drop-down menu in CB-Login only when I am offline (and not online). Currently I'm in the testing phase because I'm afraid that DJQueryMonster will prevent other plugins from working...

Yeah MooTools can cause a lot of problems as it rebinds some common global scope variables. I'm not sure why it would be loading on frontend though as it's more commonly used for some backend things in Joomla. It might be a plugin using it or beez3 (note beez3 is a very old template).

I believe the only frontend core Joomla components using it are contacts, newsfeed, and weblinks. It does look like beez3 and beez5 are just loading it in but not really using it for some reason.

Personally I recommend considering making the move to Joomla 4 in the near future, which would also mean new template and no MooTools conflicts to deal with. There's unfortunately nothing we can do about this though.

Thanks for your feedback.
I'm afraid, when moving to Joomla 4, that many things will be incompatible and I think the task is tedious... I have the impression that by deactivating MooTools, I can no longer edit my articles via the Frontend for example...

You shouldn't need to disable it globally. It just needs to be disabled in beez3 if not actually being used by beez3. Loading it on every page should be unnecessary. Default protostar template for example does not load it on every page.