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 History
Next Change →

Changes between Initial Version and Version 2 of Ticket #13065

Timestamp:: Mar 18, 2015, 4:09:56 PM (10 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #13065
- Property Status changed from new to confirmed
- Property Priority changed from High to Normal
- Property Summary changed from Integrate widgets with new copy/cut/paste datTransfer to Integrate widgets with the new copy/cut/paste dataTransfer

Ticket #13065 – Description

initial	v2
1		Widgets use copybin, while on modern browsers they can now use the dataTransfer integration which we introduced~~. Note: remember to use `editable.getHtmlFromRange()`~~.
	1	Widgets use copybin, while on modern browsers they can now use the dataTransfer integration which we introduced in 4.5.0. The question, though, is whether we have to do this, because on all IEs we'll have to leave the copybin, so we would need to branch the code. There may be a strong argument for this change - recognising content origin (internal, cross editor, external) and filtering Webkit/Blinks awful inline styles.