All users were logged out of Bugzilla on October 13th, 2018

Add per-session and per-site controls to Plugin fallback mechanism

RESOLVED WONTFIX

Status

()

P2
normal
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: Felipe, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details

(Reporter)

Description

2 years ago
The plugin fallback mechanism might need UI to allow people to disable it temporarily or permanently for a site, in order to make that website work. This is specially important during a test period where we want to measure how much people will use it, and then these controls might be kept permanently after a wider release.

It needs to be able to:
 - deactivate plugin fallback for a particular page that is loaded  (i.e., fix this once)
 - deactivate plugin fallback for a particular page/site/domain (TBD), always  (i.e., fix this always for this page)


Hopefully we can tie this to the already exisitng click-to-play UI
(Reporter)

Updated

2 years ago
Blocks: 1282490
(Reporter)

Updated

2 years ago
Blocks: 1282492

Updated

2 years ago
Priority: -- → P2
(Reporter)

Updated

2 years ago
Blocks: 1282484
No longer depends on: 1282484
(Reporter)

Updated

2 years ago
No longer blocks: 1277346
(Reporter)

Comment 1

2 years ago
To my understanding, the plan of record right now is that the fallback mechanism itself won't need UI or be user controlled. What the user will control is the global or per-site CTA setting. 

The fallback mechanism will kick automatically based on heuristics, and it's likely that there still will be an about:config pref to configure it.
No longer blocks: 1282484, 1282492
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.