Download & Extend
FCKeditor - WYSIWYG HTML editor » Issues

if processEntities = false, fckeditor insert into empty drupal extarea this: <p>&#160;</p>

Posted by igorik on February 14, 2009 at 2:11pm
Project:FCKeditor - WYSIWYG HTML editor
Version:6.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Hi

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

thanks
Igorik
http://www.somvprahe.sk

Login or register to post comments

Comments

#1

Posted by igorik on February 14, 2009 at 2:15pm

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

#2

Posted by wwalc on February 16, 2009 at 10:51am

FCKeditor bug: http://dev.fckeditor.net/ticket/2154

#3

Posted by wwalc on February 16, 2009 at 11:02am
Status:active» fixed

Actually we can handle this bug in the FCKeditor module.

#4

Posted by igorik on February 16, 2009 at 11:29am

Great!

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

thanks
Igorik

#5

Posted by System Message on March 2, 2009 at 11:30am
Status:fixed» closed (fixed)

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

#6

Posted by aharown07 on January 14, 2010 at 11:33pm

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:
http://dev.fckeditor.net/ticket/1660

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');

#7

Posted by aharown07 on January 15, 2010 at 1:11am
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?

#8

Posted by Jorrit on January 31, 2010 at 1:59pm
Status:active» closed (fixed)

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

#9

Posted by aharown07 on February 1, 2010 at 4:43am

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