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 #16676, comment 1

Timestamp:: Jan 26, 2017, 1:38:21 PM (7 years ago)
Author:: Jakub Ś
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #16676, comment 1

initial	v1
1		This is more of a feautre request than a bug ~~thus I will change it to such. At the moment we~~ don't provide support for "async".
	1	This is more of a feautre request than a bug because at the moment we simply don't provide support for "async".
2	2
	3	Anyway you are right - when async is used the {{{document.wrtie}}} should not be called. One reason is that when page has already been loaded, using {{{document.write}}} will call {{{document.open}}} which will wipe out the existing page. In such case having editor clearing a whole page doesn't sound too good.
	4