Here's what I see when I try to paste from Word 2007 into IE9.
First, pasting straight into the body field, without using the 'paste from Word' button:
- Get a dialog that asks me if I want to allow the webpage to access the clipboard. (I say 'allow')
- Get a dialog that asks me if I want to clean up the text because it's from Word. (I say 'yes')
- Get the Paste from Word overlay, but it doesn't load properly -- no place to paste.
- If I click 'cancel', the button depresses but nothing happens.
- If I click the close icon, nothing happens.
I am able to reload the page and start over at step 1.
On a second try, but with 'no' at 2:
- Get a dialog that asks me if I want to allow the webpage to access the clipboard. (I say 'allow')
- Get a dialog that asks me if I want to clean up the text because it's from Word. (I say 'no')
- Get a dialog that asks me if I want to allow the webpage to access the clipboard. (I say 'allow')
- Copy is pasted into the field.
- Click 'Save' or 'Preview' and copy is not saved.
Here are some other things that happen:
- When I click the 'source' button, it doesn't go into source view.
- When I click the 'switch to plain text editor' link, it doesn't go into plain text mode.
Any suggestions? (Please note that this is D5; an upgrade is not going to be an acceptable solution for this client.)
Comments
Comment #1
Jorrit commentedMy suggestion is that you try another editor, which may be hard to get for Drupal 5, because FCKeditor was developed well before IE9 was released.
Comment #2
escoles commentedYeh. That's where I'm heading. Waiting to hear back from the client to make sure I'm seeing problems similar to hers.
Logistically this is complicated by the fact that we haven't had a regular paid relationship with this client for a couple of years. Upgrading Drupal is not really an option; getting another editor to work shouldn't be a problem, but FCkeditor/CKeditor are the only ones I've worked with in a couple of years, I don't even know where the others are at with Word-pasting. So I was leaning toward WYSIWYG for D5, even though it will degrade their experience somewhat due to the lack of toolbar configurability, just because I can test editors on the fly that way.
Leaving this as a bug basically for reference purposes, at least for now, knowing that this isn't likely to get fixed or even extensively tested -- D5 is after EOL, after all -- hard to tell where this lies, in the embedding or in the editor code, and whether FCK updates will fix it. The FCK changelogs don't mention this problem; however, in some DotNetNuke forum I found a message indicating that a newer release of FCK solved a vaguely similar problem.
Trying to get the client to agree to pay for an FCK upgrade; if they go for it and that fixes things, will change this from bug to support request & close. They may opt to go straight to WYSIWYG/CKEditor, in which case I'll just close the issue.
Comment #3
Jorrit commentedI don't think this is a module issue, it looks like a FCKeditor (EOL too) issue. You can try to see if it works or not in a plain FCKeditor instance in am HTML page.
Comment #4
Jorrit commentedComment #5
escoles commentedThis was a bug. The version of FCK installed on their site worked in IE8 and IE9 when loaded via other means.