Changes between Initial Version and Version 1 of Ticket #13071
- Timestamp:
- Mar 19, 2015, 4:46:38 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13071 – Description
initial v1 1 All application I test s hasa different behavior for copy and paste and for drag and drop.1 All application I tested have a different behavior for copy and paste and for drag and drop. 2 2 3 * After **paste**, caret is **at the end** of the pasted content (what make sense, user most probably wantto start typing there).4 * After **drop**, drop content **is selected** (what also make sense, because it may happen that user drop the content in not exactly correct position and wantto drag it again).3 * After **paste**, caret is **at the end** of the pasted content (what makes sense, user most probably wants to start typing there). 4 * After **drop**, dropped content **is selected** (what also makes sense, because it may happen that user drops the content in not exactly correct position and wants to drag it again). 5 5 6 At the moment we always put the caret at the end, handle the drop in the "paste" way. The problem is that now `insertHtml` set the selection and this method does not what operation causes insertion. Fortunately paste event has such information, so the selection should be done by paste event ofinformation about the type of the selection should be passed to the `insertHtml`. The second way seems to be better because of backward compatibility.6 At the moment we always put the caret at the end, handle the drop in the "paste" way. The problem is that now `insertHtml` set the selection and this method does not know what operation causes insertion. Fortunately paste event has such information, so the selection should be done by paste event or information about the type of the selection should be passed to the `insertHtml`. The second way seems to be better because of backward compatibility.
