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 #9578, comment 4

Timestamp:: Feb 13, 2013, 12:16:17 PM (12 years ago)
Author:: Jakub Ś
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9578, comment 4

initial	v1
7	7	Yes, chancing the "block" definition of all paragraphs in a page is not a common practice. Personally I haven’t seen such use case anywhere.
8	8
9		There is huge number of cases that could bring similar issues. It is impossible for the editor to handle them all. We do some level of fixing for most common cases. This is just not one of them.
	9	There is huge number of cases that could bring similar issues. It is impossible for the editor to handle them all. We do have some level of fixing for most common cases. This is just not one of them.
10	10
11	11	Simple solution and correct one is using spans – inline elements by definition. That way editor will have no problem processing them.