If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Even with user.js set as directed, copy, cut and paste do not work

UNCONFIRMED
Unassigned

Status

()

Firefox
Preferences
--
major
UNCONFIRMED
7 years ago
6 years ago

People

(Reporter: efrulla, Unassigned)

Tracking

4.0 Branch
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0

Thank you so very much for the big brother approach to my security concerns.  I am old enough and mature enough to determine what site I want to cut and paste from.

I set up user.js as directed and cut, copy and paste still do not work.

Following is my user.js

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

I have also tried setting the sites to "http://www.northcountryridermagazine.com/cms" which is the cms portion of the web site and that does not work either.

Any help would be appreciated.  I like Firefox but if this is going to be an issue then then I will be forced to switch browsers.


Reproducible: Always

Steps to Reproduce:
1.Log into a site with rich text editing
2.Highlight some text
3.attempt to copy and get the pop-up stating that copy and paste are not supported.
4. Shutdown Firefox and remove from tool bar.
5. Find the Firefox profile directory and create user.js
6. Restart Firefox.  
Actual Results:  
Copy and past still not supported

Expected Results:  
Should be able to copy and paste

Updated

7 years ago
Version: unspecified → 4.0 Branch

Comment 1

6 years ago
Could be a duplicate of bug #261117
You need to log in before you can comment on or make changes to this bug.