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

Timestamp:: Nov 27, 2013, 4:19:42 PM (11 years ago)
Author:: Frederico Caldeira Knabben
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11219, comment 4

initial	v1
1	1	I think that using the "paste" event for it makes sense. It'll help simplify things.
2	2
3		So, what if we would send the paste/drop point to the event unified and a range, which can be manipulated by event listeners to move the pasted/dropped element to a different position, if necessary?
	3	So, what if we would send the paste/drop point to the event unified as a range, which can be manipulated by event listeners to move the pasted/dropped element to a different position, if necessary?