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 #13453, comment 9

Timestamp:: Jun 26, 2015, 10:25:16 AM (10 years ago)
Author:: Szymon Cofalik
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #13453, comment 9

-                      initial
+                      v1
 My approach was the one suggested by Reinmar.
 ) As he said, this is a different case so we won't include it into range affecting.
 ) Changing `isDropRangeAffectedByDragRange()` would require writing special tests for that function and some cases that are now passing might fail (this was my experience when I started to mess with `isDropRangeAffectedByDragRange()` even though I was pretty sure that my change is actually fixing real-world scenarios)
 ) Aborting the script is most similiar to what browser do when we drag onto selection.
 ) @a.delura: we would have to change drop position to either start or end of drag range which would result in same content as when aborting script, but we would additional fire events and create snapshots, which are not needed.