Closed Bug 1530543 Opened 6 years ago Closed 6 years ago

What percentage of extensions are allowed to run in private windows?

Categories

(Data Science :: Investigation, task)

x86
Windows 10
task
Not set
normal
Points:
2

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mconca, Assigned: wbeard)

Details

Brief Description of the request:
I want to know what fraction (percent) of installed extensions are users allowing to run in private browsing windows.

Right now, every extension is allowed to run in every window, private and non-private. Starting in Release 67, Firefox will disallow newly installed extensions from running in private browsing windows by default (extensions already installed will still retain their ability to run in private windows). When an extension is installed in 67 or later, the user will have to explicitly grant it permission to run in private windows.

Over time, I would expect to see the percentage of extensions allowed in private windows to drop from 100% (in releases 66 and earlier) to some lower number, but probably not zero (since certain extensions like password managers and ad-blockers are still useful in private browsing).

Any timelines for the request or how this fits into roadmaps:
The change will occur with release 67, which is in Nightly now. It might be good to get a preview in Beta, but the real data should come when 67 hits the Release channel.

Links to any assets (e.g Start of a PHD, BRD; any document that helps describe the project):

Name of Data Scientist (If Applicable):
I've worked with Ben M. in the past for add-on related questions.

Component: General → Investigation
Assignee: nobody → wbeard
Status: NEW → ASSIGNED
Points: --- → 1
Points: 1 → 2
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.