I found this ugly bug when I set processEntites to false - after then FCKeditor insert <p>&#160;</p> to start empty textarea in node/add or node editing, whatever.

if I switch off fckeditor from textarea I can see this element <p>&#160;</p>.
The big problem is that with this empty element, I can't test required textarea fields, because with this it always pass

btw doesn't matter if processEntites = false is set in drupal fckeditor.config.js or directly in fckconfig.js



igorik’s picture

you can see the full empty element in title of this bug, in body it was changed to <p> </p>

wwalc’s picture

wwalc’s picture

Status:Active» Fixed

Actually we can handle this bug in the FCKeditor module.

igorik’s picture


Probably is it what you wrote in previous bug, you will be catch empty tags?


Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

aharown07’s picture

For the benefit of anyone else who runs into this:
The problem still exists in Fckeditor 2.6.5 (I mean the editor not the module). ...and occurs in Chrome as well as FireFox due to something going on in the gecko js file.

Anyway, the fix posted below does work, though I'm not sure yet what sort of side effects it might produce:

Since its hard to pick the fix out of all the stuff there, here's the relevant portion:

Another step forward: (create a simple <br /> instead of <br type="_moz">)

Open: fckeditor/editor/js/fckeditorcode_gecko.js Row: 36
Find: {var B=A.createElement('br');B.setAttribute('type','_moz');return B;}
Delete: B.setAttribute('type','_moz');

aharown07’s picture

Status:Closed (fixed)» Active

OK... no, that's not a good idea. Result is lots and lots of <p>&#160;</p> and other anomolies all over the place.
Anybody know a real fix for this?

Jorrit’s picture

Status:Active» Closed (fixed)

Now, but it's really a FCkeditor problem, not a module problem

aharown07’s picture

Is there any way the module can compensate for the editor problem? They don't seem to be planning on fixing it over there.