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

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #14819, comment 3

Timestamp:: Aug 24, 2016, 10:50:56 AM (8 years ago)
Author:: kkrzton
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #14819, comment 3

initial	v1
31	31	Total of 34 tests failing.
32	32
33		The best approach seems to be resolve core issues first because they may be the cause of other tests (Plugins and Tickets group) failing. Also we should keep in mind that some failing tests may be the result of IE/Edge workarounds applied earlier (as Edge may have improved the workarounds may no longer be needed).
	33	The best approach seems to be resolve core issues first because they may be the cause of other tests (Plugins and Tickets group) failing. Also we should keep in mind that some failing tests may be the result of IE/Edge workarounds applied earlier (as Edge may have improved, the workarounds may no longer be needed).