We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community. If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub. At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

I removed almost all FF2 and FF3 leftovers. The last place where .cke_browser_gecko18 appears is compressed css in tt/4463 in test project. Since this test does not work I will not modify it. IMO it should be removed.

Because we dropped support for IE6 & IE7 but we still support IE QM we have a lot of checking if browser is in IE QM and this checking was implementend in multipile ways (unsing env.ie && env.quirks or env.ie6Compat or document.documentMode). So I introduced new variable: env.ieQuirks and replace all of the above.

I'm not sure if there is a point in keeping env.quirks == true for non-IE browsers. Maybe env.quirks should be true only in IE 8 and IE 9 QM (as env.ieQuirks works now).

The problem with quirks appeared after removing IE 6 & IE 7 support, because most of hacks now apply only to QM (instead of IE 7, IE 6 and IE QM). I think that it would be misleading if we keep if ( env.ie6Compat ) in our code only because of QM (env.ie6Compat is true in QM) and it is better to replace it with if ( env.ieQuirks ). Also after clean up we can save some bites (compressed ckeditor is 322 bits smaller with env.ieQuirks).

Anyway I introduced env.ieQuirks in separate commit so it could be easily removed.

Thanks for clarification why you did this change - it of course makes sense. But it doesn't mean that it has to be done in unrelated ticket. So please extract these changes to separate ticket and let's discuss whether we want to make them now.

I fixed these issues and rebased branch. We decided to remove cke_browser_ie6 so now I QM editor will get only cke_browser_iequirks class instead of both cke_browser_ie6 cke_browser_iequirks. Changes are I separate commits to make review easier. After review I will join them with previous commits.

This commit makes sense here, but in the context of whole branch (with previous changes). I rebased and squashed commits to avoid such confusing commits. Also I rebased branch onto newest major, after merge master into it.

We made a decision to keep all IE7 related hacks and isCompatible==true when version==7. This way we'll keep current, decent CKEditor support for IE7 and IE compatibility mode. However, this is "unofficial" support, so the goal is not to improve it in the future, but to not lose it.