DOM parsing error in IE
|Reported by:||screwtape||Owned by:|
|Component:||Project : MediaWiki+FCKeditor||Version:||FCKeditor 2.6.4|
First of all, we are using MW1.10, started with FCKeditor V2.5.1, Build 17566, and later V2.6.4, build 21629.
Problem is this, we have a simple nested list of text, when we place the cursor next to some existing text, backspace over it, type some new text and then attempt to switch to wikitext we get an illegal argument error in the plugins/mediawiki/fckplugin.js file
[NOTE: error information is from using V2.6.4]
The line in question is line 758, illegal argument: var parentIsSpecialTag = htmlNode.parentNode.getAttribute( '_fck_mw_customtag' ) ;
*[[Section1|Section1]] **Test stuff **June **May more stuff
*[[Section1|Section1]] **SImple stuff **June **May<span id="fck_dom_range_temp_1245248294310_734" /><span id="fck_dom_range_temp_1245248294310_48" /></span> more stuff
As you can see, there is a lot of "fck_dom_range_temp_" garbage being introduced when the error occurs. I've chased the error in the code and from what I can tell, the problem crops up when the append node function is called with a nested HTML DOM object that has no defined parent or data value.
If you submit this information, you get some of the HTML incorrectly rendered as text, and some rendered correctly as HTML.
I only see this IE, FF exhibits the correct behavior.
I attempted to replicate the problem in the sandbox, but had no luck. I downloaded the latest nightly build and worked with that but get the same error with that version (2.6.4) as well. If I avoid backspacing over the word, and instead double click or mouse select text and retype the problem does not occur.
The thing that is really maddening about this, is that the issue just started. Everything worked up until the end of last week, and nothing has changed, except perhaps, IE in an MS update. The other aspect is that this error is not consistent, though I can eventually get it replicate, and usually at the worst possible time (murphy's law). At this point I don't know what to do except tell folks to use FF instead of IE, which is not a possibility for some of our clients. Any attention to resolving this issue would be appreciated.