Opened 11 years ago
Last modified 10 years ago
#11427 confirmed Bug
[IE8] Many "Invalid argument" errors when beginning of the document is removed
Reported by: | Piotr Jasiun | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 4.0 |
Keywords: | Cc: |
Description (last modified by )
- Open replacebyclass.html sample in IE 8.
- Select content: from strike through
three and
up to the begging of the document. - Press Ctrl+C or Delete.
Result:
Error: Invalid argument
and Browser crash.
The same in inline.
IE9 and Chrome works fine.
Since 4.0.
Attachments (2)
Change History (11)
Changed 11 years ago by
Attachment: | 11427-ie8-Browser-crash-when-begging-of-the-document-is-removed.webm added |
---|
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 11 years ago by
Status: | new → confirmed |
---|
comment:4 Changed 11 years ago by
Milestone: | → CKEditor 4.3.3 |
---|
We need to investigate this issues.
First of all - using git bisect, because it may give us some idea what change (most likely some completely unrelated one) caused this.
comment:5 Changed 11 years ago by
I get a browser crash because of debugging configuration. With the default settings you should get "only" plenty of "Invalid argument." errors.
comment:6 Changed 11 years ago by
Summary: | [IE8] Browser crash when begging of the document is removed → [IE8] Many "Invalid argument" errors when begging of the document is removed |
---|
comment:7 Changed 11 years ago by
Summary: | [IE8] Many "Invalid argument" errors when begging of the document is removed → [IE8] Many "Invalid argument" errors when beginning of the document is removed |
---|
comment:8 Changed 11 years ago by
Milestone: | CKEditor 4.3.3 |
---|
Unfortunately this issue is a very serious IE's bug. I triggered it without any plugins:
var editor = CKEDITOR.inline( 'editable', { plugins: '', allowedContent: true } );
and in both kind of editors. IE starts to throw errors for nearly every DOM operation, so I don't see a place where we could handle it with try-catch.
I even triggered it on native contenteditable with one line of selection#getRanges
. See 11427.html.
However, to trigger this, we need very precise HTML. Even a space after image is important! And there has to be an inline element inside second paragraph. And image has to be floated. Therefore, I don't see this as a bug for which we should waste more time.
Changed 11 years ago by
Attachment: | 11427.html added |
---|
Screencast attached.