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

Timestamp:: Feb 27, 2015, 7:49:05 AM (9 years ago)
Author:: Artur Delura
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #12619, comment 3

v1	v2
1		To allow drop on empty document we are forced to listen to {{{dragover}}} event on {{{CKEDITOR.document}}} and prevent default browser behaviour~~. Since issue seems quite easy to fix, there is an issue that we are interferencing DOM element which is a~~ CKEDTIOR property.
	1	To allow drop on empty document we are forced to listen to {{{dragover}}} event on {{{CKEDITOR.document}}} and prevent default browser behaviour when fired. Since issue seems quite easy to fix, there is an issue that we are interferencing DOM element which is not an CKEDTIOR property.
2	2
3	3	I think this shouldn't be a default behaviour. We should add an option config, which will let user decide whether he or she want us to prevent default browser behaviour.