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.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

Changes between Version 1 and Version 2 of Ticket #11422, comment 9

Timestamp:: Jan 21, 2014, 2:56:46 PM (11 years ago)
Author:: Piotr Jasiun
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11422, comment 9

v1	v2
1	1	A finished and pushed IE cleanup, so this task is basically done.
2	2
3		Because we drop 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.
	3	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.
4	4
5	5	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).