1275246 - Document the dom.allow_cut_copy preference better

Status: NEW

(Core :: DOM: Events, defect, P5)

Description

[Nika Layzell [:nika] (ni? for response)]

The dom.allow_cut_copy pref which was added in bug 1170911 to allow the user to disable document.execCommand('cut'/'copy') for web pages isn't very well documented. It also doesn't appear in about:config as a string, instead it needs to be added manually.

Because of its low discoverability, people online seem to believe that we don't have the ability to disable this behavior, which is unfortunate. It should probably be added to about:config, and should be documented in the relevant places.

I also feel like the name is unfortunate, as we aren't disabling cut or copy, but rather disabling the ability for the document to initiate them itself. Cut and copy work as normal through the menus or keyboard shortcuts.

Comment 1

[Nika Layzell [:nika] (ni? for response)]

What do you think ehsan?

Comment 2

[Xidorn Quan [:xidorn] UTC+11]

Ehsan expressed his concern clearly in bug 1170911 comment 5, and I wouldn't be surprised if he still insists this should be a hidden pref.

I agree with you that it should be more discoverable.

Comment 3

[(no longer active)]

Who are the people online?   :-)

I understand your grievances, but I'm not sure what exact problem you're trying to solve and what are you proposing...  Can you please elaborate?

Comment 4

[Nika Layzell [:nika] (ni? for response)]

(In reply to :Ehsan Akhgari (busy, don't ask for review please) from comment #3)
> Who are the people online?   :-)
> 
> I understand your grievances, but I'm not sure what exact problem you're
> trying to solve and what are you proposing...  Can you please elaborate?

The reasoning goes something like this: 
 a) This config option doesn't really break the internet very much. All it does is make it so that people's copy buttons don't work, which usually isn't a core part of the product. Compared to something like disabling cookies (which is in about:preferences still IIRC), it doesn't really blow anything up.
 b) There are people who are paranoid about things like copyjacking and don't want websites to be able to modify their clipboard. They are currently disabling the clipboardevents pref to get rid of `oncopy` etc, and also want to be able to disable `execCommand('copy'/'cut')`.  Especially because the config option doesn't really break anything severe I feel like allowing people to minorly break parts of the internet for some piece of mind could be worth it. 

It's not a severe thing, but I feel like keeping the pref hidden to protect people from toggling it is a bit silly, especially considering how little toggling it will break.

Comment 5

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, 4 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.