TinyMCE converts cellspacing to cellSpacing

[oliver341]

Hi all, whenever I edit some xhtml with TinyMCE in CMSMS I find it always converts "cellspacing" to "cellSpacing" which is very annoying because this isn't xhtml compliant. There are other attributes which get converted like this.

Please could someone tell me where to go to change this behaviour?

[Pierre M.]

Hello,

Code: Select all

egrep -r cellSpacing cmsmadesimple-1.2.3/ | sed -e 's/\:.*//' | sort | uniq

outputs :

Code: Select all

cmsmadesimple-1.2.3/modules/TinyMCE/tinymce/jscripts/tiny_mce/plugins/
simplebrowser/connectors/test.html
simplebrowser/frmactualfolder.html
simplebrowser/frmcreatefolder.html
simplebrowser/frmfolders.html
simplebrowser/frmresourceslist.html
simplebrowser/frmresourcetype.html
simplebrowser/frmupload.html
table/jscripts/table.js

With an additionnal "| wc -l" it tells you have 8 files to patch for cellSpacing.

Pierre M.

[oliver341]

Hi Pierre, I've just tried editing my site in Firefox, and in Firefox TinyMCE does not rename cellspacing to cellSpacing. In Internet Explorer however, cellspacing is renamed to cellSpacing.

For instance, I edit some table html in non-WYSIWYG mode, turn WYSIWYG mode on, then off again. cellspacing is then renamed to cellSpacing. Why would Internet Explorer do this? And do I understand correctly that searching and replacing all occurances of cellSpacing in the TinyMCE code is the fix? Thanks.

[oliver341]

I have search and replaced all occurances of cellSpacing within CMSMS, and the TinyMCE cellspacing -> cellSpacing problem is still happening. If Internet Explorer itself is converting cellspacing -> cellSpacing it's a very strange bug.

[Pierre M.]

Very strange !
Seems a bug in IE to me. MS is kidding us again.
Or... have you cleared your browser's cache ?

Pierre M.

[oliver341]

It doesn't appear to be a browser cache issue, because the cellspacing -> cellSpacing conversion occurs even with toggling the "Use WYSIWYG" button, which is purely a Javascript operation. It does seem to be a bug in IE, but I wonder why a Javascript implementation would need to make this conversion internally.