"Computers are useless, they can only give you answers." Pablo Piccaso
Published on September 23, 2008 By SKoriginals In Forum Issues

Alright, just noticed this tonight for the first time. I'm recently and slowly converting to FF as v3 is growing on me. However, I commonly use the 'Right-click > Copy'  (or cut and/or paste) options. Just got used to doing so instead of the key short-cuts Ctrl+c (or x or p or whatever).

Now when using the key short-cut method everything is fine and dandy but when using the right-click method you get the following error (which I'll take a sceenshot of right now)....

Notice its a screenshot of me writing this message 

ok, the link takes me to this page for an explination and 'fix'... http://www.mozilla.org/editor/midasdemo/securityprefs.html

Well that just seems absurd that that even needs to be done, so if there is something that can fix that 'issue' on the sites end that would be a good idea I think. 

 


Comments (Page 1)
on Sep 23, 2008

Yeah....this has been bugging ma as well!

 

on Sep 23, 2008

And the fix doesn't work explained on that page......much like the edit button here...or a lot of other stuff in the forums now.

on Sep 23, 2008

Yeah, it's strange that it doesn't work.

 

But ctrl+c and ctrl+v work perfectly, so use that instead.

on Sep 23, 2008

And the fix doesn't work explained on that page

Most likely the tinymce devs have it coded to not even try, since unless someone has specially set it to allow, since javascript clipboard access is prohibited in Gecko browsers by default.

Anyway, you can still use Ctrl+X/C/V just fine, since those are manual user-triggered shortcuts.

on Sep 23, 2008

you can still use Ctrl+X/C/V just fine, since those are manual user-triggered shortcuts.

Yeah....but those are a pain in the butt when you can rightclick faster.

on Sep 23, 2008
user_pref("capability.policy.policynames", "allowclipboard");
user_pref("capability.policy.allowclipboard.sites", "http://www.mozilla.org");
user_pref("capability.policy.allowclipboard.Clipboard.cutcopy", "allAccess");
user_pref("capability.policy.allowclipboard.Clipboard.paste", "allAccess");

Boy oh boy. It's obvious why it doesn't work here. Look at the second line only mozzilla.org is being added as allowclipboard.sites in their example. You have to add "http://forums.wincustomize.com to get it to work here.
on Sep 23, 2008
Boy oh boy.  It's obvious why it doesn't work here.  Look at the second line 
only mozzilla.org is being added as allowclipboard.sites in their example.
You have to add "http://forums.wincustomize.com to get it to work here.

Argg! please fix the edit.

Don't know why I had to manually format that line????
on Sep 23, 2008

This is a test.

Don't know why I had to manually format that line????

It's working here.
on Sep 23, 2008

This is what my user.js file looks like:

user_pref("capability.policy.policynames", "allowclipboard");
user_pref("capability.policy.allowclipboard.sites", "http://www.forums.wincustomize.com");
user_pref("capability.policy.allowclipboard.Clipboard.cutcopy", "allAccess");
user_pref("capability.policy.allowclipboard.Clipboard.paste", "allAccess");

I also have javascript enabled.

FF3 right click copy and paste is working here for me on these forums.

on Sep 23, 2008

Yep. It's a 'security measure' employed by Mozilla. Not an actualy bug in the editor or the forums persae, even though it may be percieved as a bug. The workarounds that BigDogBigFeet and kryo outlined do work pretty well (thanks guys).

much like the edit button here...or a lot of other stuff in the forums now

Just a friendly request guys; please hold off on posting commentary like that in posts in the Forum Issues category. It's demoralizing and it doesn't help with resolving the actual issue, or helping someone to get a workaround working. It's also pretty off topic. There are quite a few posts right now about the edit button not working, and this particular post isn't the proper place to comment on that issue. Please help us out in this regard and have a little restraint. We know that issues can be frustrating, but the people on the other side of the screen are human too.

on Sep 23, 2008

It's demoralizing and it doesn't help with resolving the actual issue, or helping someone to get a workaround working. It's also pretty off topic.

You're right.  Does no good to beat something to death in every forum post.

on Sep 23, 2008

The workarounds that BigDogBigFeet and kryo outlined do work pretty well (thanks guys).

I know it 'will' work, hell I even posted the link to the page with the 'work-around'. I was just wondering if there was something that could be done on the sites end.  Thats all

on Sep 23, 2008

Oh well SK your post didn't make that clear and Web's clearly said their example doesn't work at all.  If anyone can answer your question regarding how to get that facility to work over a number of web sites it would be Mozilla.  I'm not why you would think there was something that the site could do given that this is a security feature in FF3 that Mozilla has put in place that specifically was made to prevent a web site from controlling that function thru javascript.

on Sep 23, 2008

If anyone can answer your question regarding how to get that facility to work over a number of web sites it would be Mozilla.

As you say, I wouldn't bet on it. Being able to remotely override a security setting kinda defeats the point of having one.

on Sep 23, 2008

As you say, I wouldn't bet on it

I haven't asked them but, I'm thinking what SK indicated in his initial post would be their response and would go something like this. 

"You have to enumerate each site you want this facility to be active for in your user.js file"

I'm just saying.

Meta
Views
» 4325
Comments
» 20
Category
Sponsored Links