Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi
I found this ugly bug when I set processEntites to false - after then FCKeditor insert <p> </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> </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
Comments
Comment #1
igorik CreditAttribution: igorik commentedyou can see the full empty element in title of this bug, in body it was changed to
<p> </p>
Comment #2
wwalc CreditAttribution: wwalc commentedFCKeditor bug: http://dev.fckeditor.net/ticket/2154
Comment #3
wwalc CreditAttribution: wwalc commentedActually we can handle this bug in the FCKeditor module.
Comment #4
igorik CreditAttribution: igorik commentedGreat!
Probably is it what you wrote in previous bug, you will be catch empty tags?
thanks
Igorik
Comment #6
aharown07 CreditAttribution: aharown07 commentedFor 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:
Comment #7
aharown07 CreditAttribution: aharown07 commentedOK... no, that's not a good idea. Result is lots and lots of
<p> </p>
and other anomolies all over the place.Anybody know a real fix for this?
Comment #8
Jorrit CreditAttribution: Jorrit commentedNow, but it's really a FCkeditor problem, not a module problem
Comment #9
aharown07 CreditAttribution: aharown07 commentedIs there any way the module can compensate for the editor problem? They don't seem to be planning on fixing it over there.