Bug 12243 – FCKeditor: Paste buttons are always disabled

• Component: HTML Editing
• Status: RESOLVED DUPLICATE

The paste (Normal Paste, Paste as Plain Text and Paste from Word) buttons never get enabled in the toolbar or in the context menu.

[Justin Garcia]

*** This bug has been marked as a duplicate of 11335 ***

(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of 11335 ***
> 

Justin, this bug seams to be related to queryCommandEnabled('Paste'), not to execCommand('Paste').

The 'Paste' command is one of commands defined in the execCommand "standards". So, it is extensively adopted. Here we have many things to think about. I'll try to give some justifications to make queryCommandEnabled work properly in this case, reflecting the Firefox behavior.

Even if WebKit decides that the execCommand('Paste') will never paste user's data, for security reasons (even if the user wanted that), queryCommandEnabled('Paste') is quite useful for us to understand that there is data available in the clipboard. So, it would be ok if queryCommandEnabled('Paste') returns "true" and execCommand('Paste') returns "false".

In FCKeditor, this is important so we can enable the interface buttons for pasting (using queryCommandEnabled). If we try to paste and execCommand returns false, we display a dialog to the end user, asking her to paste in that dialog by using the keyboard shortcuts. This is the current behavior with Firefox, and it would be wonderful to have it working in the same way with Safari.

I'm adding a TC to it, which shows the Safari X Firefox difference.

Created attachment 14977 [details]
TC

[Justin Garcia]

I have a fix for this that Geoff has reviewed.  I'll be checking it in soon.

[Eric Seidel (no email)]

Just curious whatever happened to Justin's fix... did it get checked in?  The test case still fails on TOT.

[Justin Garcia]

This *is* a dupe of 11335 as far as I can tell.  The test case outputs false for queryCommandEnabled('Paste') because it *is* disabled, because of the security concerns mentioned in 11335.  Frederico, if I've got this wrong, please reopen.

*** This bug has been marked as a duplicate of 11335 ***

In theory, the current behavior is correct. In practice, it is a problem for us, as there is now way for us to simply know that there is data available in the clipboard (see comment #2). So now it is up to you guys (even if I can predict the way you are going to take with it).