compatibility with BUEditor

it might be related with #747616: Compatibility with WYSIWYG

I can't follow the discussion on the WYSIWYG issue.

I wasn't expecting you to follow the other issue, just taking a note for myself.

Will there be a change to this module?

I hope so, but I haven't reviewed this yet.

I've reviewed and located the cause of this issue
right now I can provide a patch that will make BUEditor work
but this is only temporal, I should come with something else
(if you check the patch, you'll see that there is only a line being commented out, to avoid switching back ids)

This works for me too, thanks. However, the patch isn't general in it's current form - there should be some check if BUeditor is used and only then should _comment_driven_restore_ids be skipped. Or _comment_driven_restore_ids needs to be reviewed - is there a bug?

the patch isn't general in it's current form

it is a temporal workaround (as noticed in the patch's filename)

Or _comment_driven_restore_ids needs to be reviewed - is there a bug?

indeed, it needs to be revisited

if I recall correctly, _comment_driven_restore_ids was born as a proposal for #733354-8: parents' names should be form_clean_id compliant (i.e. no colon) and there is no other (known) purpose for it
(see also #928812-11: Compatibility with CKEditor)

more likely the proper answer lies behind #747616-5: Compatibility with WYSIWYG

@arhak: Just for the record, the reason I wrote "the patch isn't general in it's current form" was to justify that I changed status from "reviewed & tested by the community" to "needs work". Your patch/comment is very clear about not being a permanent fix.

fyi , The patch causes breaks Notifications posted from comments. Once you disable the line , selection of notifying users don't work ( e.g. everyone who uses OA). I suspect that it can cause issues with other modules that their data interfere with driven comment. It took me a while to figure it out so if anyone faces similar behavior, just revert.