AFAIK the 4.9 RC1 version we're dogfooding here contains an updated version of fckeditor that works with google chrome , whereas the old one does not for some reason - this is likely to be due to some incompability or non-standard code that google chrome has problems with (it is it's first release and in their blog post they noted that they're only getting 99% coverage of the million of so test sites they used - and as none of these sites have log in's I would suspect that none had a public fckeditor available). I'm guessing that due to fck's popularity, google will notice this lapse and fix it in a future release.

Cathal

actually as google wrote their own js processor (v8) it's as likely that the issue is their parser as in existing javascript. Considering that fck works on IE and firefox which have well over 95% of the market that makes them the defacto standard so any new browser should support javascript supported by those 2 or else support an ECMA standard, and not some arbitrary set of js. Anyway, it doesn't really matter as the new fckeditor release, along with 4.9 which contains it will be out soon.

Cathal