Drag and drop of textual content and widgets #9128
Comments
niegowski
added
type:feature
|
|
|
@niegowski Game changing Thx alot |
|
What do you think of adding a drag indicator possibility (it can automatically select the block)? I think it is nice for the UX.
|
|
@castroCrea If I understand correctly, these are scenarios C and D from #2664 and outside the scope of the current work. There's dedicated #7731 for the block-level dnd. |
|
The cool thing is that @niegowski managed to make block widgets draggable in an inline-manner, but with what I think is a reasonably good UX. So it's not yet a proper block-level drag&drop, but it's a major improvement over what's currently completely impossible. |
|
Awesome stuff, I've been working on my own solution based on using text ranging, but it doesn't seem to be viable. I may end up going with block level only. |
Feature (clipboard): Implemented the basic content drag and drop support. Closes #9128. Feature (clipboard): The `contentInsertion` event is fired from `ClipboardPipeline` to enable customization of content insertion (see #9128). Other (clipboard): The paste as plain text feature was extracted to the dedicated `PastePlainText` plugin (see #9128). Other (engine): The `mouseup` event is fired by the `MouseObserver` (see #9128). Other (table): The `mouseup` event is no longer fired by the `MouseEventsObserver` from the ckeditor5-table package (now handled by `MouseObserver`) (see #9128). Internal (code-block, image, link, media-embed, paste-from-office): Updated to the changes in clipboard pipeline (see #9128). Internal (widget): The `mousedown` event is no longer stopped from the default handling to enable content dragging (see #9128). BREAKING CHANGE (clipboard): The `inputTransformation` event is no longer fired by the `Clipboard` plugin, now the `ClipboardPipeline` plugin is responsible for firing that event (see #9128). BREAKING CHANGE (clipboard): The `clipboardInput` and `inputTransformation` events should not be fired or stopped in the feature code. The `data.content` property should be assigned to override the default content instead. You can stop this event only if you want to completely disable pasting/dropping of some content \[TODO migration guide link\] (see #9128).
📝 Provide a description of the new feature
Extracted from #2664. Scenario A, B, and C with the assumption that dropping is allowed only in text positions or on the widgets.
If you'd like to see this feature implemented, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: