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

Important feature broken by capability.policy

UNCONFIRMED
Unassigned

Status

()

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

People

(Reporter: RC, Unassigned)

Tracking

4.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

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

This is not really a bug, but a regression caused by the new CAPS policy feature. I just discovered that in FF4 I could no longer cut and paste while using a javascript Rich Text editor in the Moodle installation at my University. This editor is used by hundreds of instructors everyday. As instructed on mozilla.org, I edited the user.js file manually to restore the lost functionality. I consider myself above average in hacking skills and it still took me more than 10 minutes, reading a full page in mozilla.org, several restarts, and (ironically) cutting and pasting from mozilla.org to user.js in my editor to get the capability.policy to work properly. I understand the need for more secure policies, but if a feature breaks common functionality like the ubiquitous Rich Text editor, there should be an *easy* way to restore it on a site by site basis. It could be done similar to the way expired certificates are dealt with, for example, or at least a through a simple site list in Options. A user less committed to Firefox than I, will just give up and use a different browser instead of working under the hood and trying to figure it out. Thanks 

Reproducible: Always

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.