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 #11562, comment 2

Timestamp:: Aug 17, 2017, 2:07:48 PM (7 years ago)
Author:: Jakub Ś
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11562, comment 2

initial	v1
7	7	Now there's no error. And #10340 is about cases in which DTD caching makes it impossible to extend it after loading CKEditor source.
8	8
9		~~However, I agree that CKEditor could not throw error if DTD was not extended~~. Not in every scenario it's predictable what will be inserted into editor and it's not a problem to default use some default DTD (span's or p's) when element cannot be found.
	9	However, I agree that CKEditor could not throw error if DTD was not extended. Not in every scenario it's predictable what will be inserted into editor and it's not a problem to default use some default DTD (span's or p's) when element cannot be found.