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 #14239, comment 3

Timestamp:: Jan 5, 2016, 8:29:06 AM (9 years ago)
Author:: Kevin Kamel
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #14239, comment 3

v1	v2
1	1	I think there was a miscommunication here.
2	2
3		I demonstrated that entering html5 (invalid or not, depends on the circumstances) will cause CKEditor to insert ~~duplicate~~ nodes. The editor is effectively unusable as a result. Since when does CKEditor take markup and make it worse?
	3	I demonstrated that entering html5 (invalid or not, depends on the circumstances) will cause CKEditor to insert spurious nodes. The editor is effectively unusable as a result. Since when does CKEditor take markup and make it worse?
4	4
5	5	My example is just that, an example. If you play with HTML5 and custom ACF rules you are going to quickly see that there are other cases that are even worse. This is a very severe bug that prevents all but perfect HTML5 from being used with the editor.