CKEditor 3.1.1 won't load in Opera when inserting dynamicly

[Niek Kouwenberg]

When trying to load the CKEditor (version 3.1.1), in Opera (10.51) via Ajax insertion or on the fly DIV replacement, it will try to load, but gets stuck (Elements: 10/10). The editor appears fully loaded, but the entire page in unresponsive (keeps loading, links are not clickable)

This does not only apply to my own application, but also for most of the advanced samples in the CKEditor source, for example:

• Replace DIV elements on the fly
• Create and destroy editor instances for Ajax applications

I can't find any ticket addressing this issue, but it doesn't seem to affect, or is fixed, in CKEditor 3.2.

Updating to 3.2 is currently not an option, since it breaks backward compatibility for my custom skin.

[Niek Kouwenberg]

I've just tested the samples in Opera 10.01, and there it seems to work es expected. So, it only affects the latest version of Opera.

[Alfonso Martínez de Lizarrondo]

Both 3.1, 3.2 and SVN work correctly for me with Opera 10.51.

Anyway, remember that we can't port back all the fixes to 3.1 because then you just get 3.2

[Frederico Caldeira Knabben]

We're not able to help you on this. Our recommendation of course is upgrading to the latest version.

Btw, let me introduce you a nice tool: ​The CKEditor Revisions Site. You can use this site to test every single commit we made on the SVN. By doing so, it's easy to identify which release introduced you a bug, so you can also find out when it got fixed later, and the exact changes that made it.

[Niek Kouwenberg]

It's not worth the trouble of checking all revisions, I've just spent a day making my own skin and plugin compatible with 3.2. It was something I had to do anyway.

However, closing this bug as worksforme is a bit weird to me. You've release a version (3.1.1) which doesn't work in the latest version of a top-5 browser. I would say this is a major issue (possibly worth backporting for). Why would you otherwise release 3.1.1 simultaneous with 3.2, if you're not willing to provide patches for this release?

My point being: please test future releases in all major browsers. This could be easily done by just clicking through your own examples. The editor not being able to complete loading is not an issue you can easily miss.