ClosedQuestion JavaScript error makes changing options impossible - happens with WYSIWYG enabled

I can confirm this bug. I've seen it in a Checklist question. Marking critical as it makes normal use of the module pretty much impossible.

When clicking the Save button on an Option, Chrome's dev console gives me this:

Uncaught Error: NOT_FOUND_ERR: DOM Exception 8
c.extend.cleanjquery.js:125
c.buildFragmentjquery.js:121
c.fn.extend.domManipjquery.js:120
c.fn.extend.appendjquery.js:114
(anonymous function)xmlEditor.js:385
b.extend.eachjquery.js:34
b.fn.b.eachjquery.js:27
createEditorForxmlEditor.js:384
jQuery.fn.xmlTreeEditorxmlEditor.js:110
jQuery.fn.xmlTreeEditor.dataxmlEditor.js:324
c.event.handlejquery.js:64
c.event.add.h.handle.ojquery.js:57

Re-titling.

I have same problem.

I'm working on this bug today and hopefully getting it fixed sometime this week.

I'm hoping @HylkeVDS will allow me to become co-maintainer of this project so I can help with committing patches.

Seems that the CKEditor and/or WYSIWYG module are what's causing the problem on my site. If I disable WYSIWYG, the closedquestion tree editor JS works fine again.

I'm not sure how to fix it yet, though, beyond turning off the WYSIWYG module or doing some complicated form_alter() / css_alter() / js_alter() in order to rip out the WYSIWYG from closedquestion node editing pages (though there might be some easier way to exclude the WYSIWYG?)

Retitling.

Work-around: http://drupal.org/node/285200#comment-5336646. Note that *any* WYSIWYG being active on the node form causes this problem, not just if a wysiwyg is active on the body field.

I will also roll a patch soon for Closed Question that turns off WYSIWYG on the body field (which is where the XML is stored), for completeness/defensiveness. (It's a one-liner.)

I've committed a patch here that turns off the WYSIWYG for the body (XML) field.

Unfortunately, there could be other text area fields on the content type that cause a WYSIWYG to be running. It doesn't seem quite right to muck around with the settings for these other fields.

The real solution is to figure out what about the WYSIWYG is causing this problem and somehow fix it (either in the wysiwyg module or this module). But I haven't been able to find the conflict so far.

So for now: Click the "Disable rich text" links to turn off WYSIWYG editors on your ClosedQuestion node edit form before using the question editor.

Updated issue summary.

@adamdicarlo: Is this still an issue?

Please reopen if the error is still there