Opened 9 years ago
Closed 8 years ago
#13924 closed Bug (wontfix)
IE11 - Typing is slow after pasting for the second time into editor.
Reported by: | Jakub Ś | Owned by: | Tomasz Jakut |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 4.0 |
Keywords: | IE11 support | Cc: |
Description
Steps to reproduce
- Open attached 27 page document and paste it into editor.
- Start typing immediately after paste. Document is being still processed so first characters my not show up but later on you can type without problems
- Press Ctrl+A and Backspace (you can press delete and backspace few times - it doesn't matter)
- Paste text again and again after the text shows up start typing.
Actually you can wait few seconds and then start typing.
Expected result
Typing speed should be normal.
Actual result
Typing is very slow even after few minutes.
Other details (browser, OS, CKEditor version, installed plugins)
Problem can be reproduced in IE11 only. IE11 is supported from CKEditor 4.3 but I have seen this issue even in CKEditor 4.0.
Attachments (2)
Change History (18)
Changed 9 years ago by
Changed 9 years ago by
Attachment: | 2015-11-12_1054.swf added |
---|
comment:1 Changed 9 years ago by
Keywords: | support added |
---|---|
Status: | new → confirmed |
comment:2 Changed 9 years ago by
Milestone: | → CKEditor 4.5.6 |
---|
comment:3 Changed 9 years ago by
Owner: | set to Tade0 |
---|---|
Status: | confirmed → assigned |
comment:4 Changed 9 years ago by
comment:5 Changed 9 years ago by
Rather than video memory it should depend on system RAM memory. Set it simply to something like 2gb and then see the results.
Also compare how does it work for IE10, IE9, Edge - is IE11 the only one browser having this problem?
comment:6 Changed 9 years ago by
Tested it on IE8, IE11 and Edge. Among them only IE11 seems to have this "feature".
comment:7 Changed 9 years ago by
Milestone: | CKEditor 4.5.6 → CKEditor 4.5.7 |
---|
comment:8 Changed 9 years ago by
One of our users/customers have provided temporary workaround.
Recently we found out that typing becomes faster if you activate and deactivate the “Source Code” mode after pasting the large document into the CKEditor instance.
/** * Workaround for pasting problems with IE11 */ CKEDITOR.plugins.add('iepaste-workaround', { init : function(editor) { if(CKEDITOR.env.ie) { editor.on('paste', function(evt) {// Show screen lock }); editor.on('afterPaste', function(evt) { var editor = evt.editor; var bookmarks = editor.getSelection().createBookmarks2(); editor.setData(editor.getData(), { callback: function() { try { var selection = editor.getSelection(); selection.selectBookmarks(bookmarks); selection.scrollIntoView(); } finally { // Close screen lock } } }); }); } } });
comment:9 Changed 9 years ago by
Owner: | changed from Tade0 to Tomasz Jakut |
---|
comment:10 Changed 9 years ago by
It seems that problem is caused by selecting range after inserting pasted data into it. Everything works fine without touching the range.
Moreover it could be bug in IE with handling native selections as simplifying our handler for selecting ranges does not solve the problem.
comment:11 Changed 9 years ago by
Milestone: | CKEditor 4.5.7 → CKEditor 4.5.8 |
---|
This issue is really complex, we're unable to squeeze it into 4.5.7.
comment:12 Changed 9 years ago by
The problem could be easily reproduced outside the CKEditor, as shown in that demo.
Bug was reported to MS.
comment:13 Changed 9 years ago by
Milestone: | CKEditor 4.5.8 → CKEditor 4.5.9 |
---|
comment:14 Changed 8 years ago by
Milestone: | CKEditor 4.5.9 → CKEditor 4.5.10 |
---|
comment:15 Changed 8 years ago by
Issue in IE's bug tracker is marked as won't fix. Therefore, unfortunately, we are not able to do any more without Microsoft support.
comment:16 Changed 8 years ago by
Milestone: | CKEditor 4.5.10 |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
I did a few test, here are the results:
-Going through the steps on a VirtualBox VM with 128MB video memory reproduces the problem even at step 2.
-Changing the video memory to 256MB (max available) makes the problem appear at step 4.
-After step 4. the profiler shows, that the vast majority of processing power is dedicated to handling the native innerHtml method.