Opened 16 years ago
Last modified 16 years ago
#2759 confirmed Bug
error when perfroming drag and drop in ie
Reported by: | Lisa | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | FCKeditor 2.6.3 |
Keywords: | IE | Cc: |
Description
ie throws javascript error: Incompatible markup pointers for this operation
This occurs when drag and drop action takes place from the same browser window the editor is currently running. Additonaly the formating remains even with ForsePasteAsPlainText set as True.
Attachments (1)
Change History (6)
comment:1 Changed 16 years ago by
Keywords: | Pending WorksForMe added |
---|
comment:2 Changed 16 years ago by
Open IE with a url that contains FCKeditor enabled in a textarea. Select copy, images and links from the same page you are on - in the same browser. Drag your selected area into FCKeditor. Javascript error displays. If FCKeditor has ForsePasteAsPlainText set as true - not only do you get the Javascript error, but it does not force the plain text. All links and images will display in the editor area.
comment:3 Changed 16 years ago by
I was unable to reproduce this bug in IE7 (vista 32). Could you try it with demo: http://www.fckeditor.net/demo and give your results?
comment:4 Changed 16 years ago by
I tested using your demo - but apparently ForcePasteAsPlainText = true is not set in the demo's cofiguration file. Test again setting ForcePasteAsPlainText = true and you should be able to reproduce this issue. I am using ie7 on windows XP.
comment:5 Changed 16 years ago by
Keywords: | Confirmed IE added; Pending WorksForMe removed |
---|---|
Priority: | High → Normal |
Yes. Finally I can confirm this bug.
1- Open IE
2- set ForcePasteAsPlainText = true
3- select text and drag and drop it onto the editor
Result: error line 196
194 // Paste a marker element at the collapsed range and get it from the DOM. 195 var sMarkerId = 'fck_dom_range_temp_' + (new Date()).valueOf() + '_' + Math.floor(Math.random()*1000) ; 196 oRange.pasteHTML( '<span id="' + sMarkerId + '"></span>' ) ; 197 198 return doc.getElementById( sMarkerId ) ;
Could you provide some steps to reproduce this bug?