Open Bug 1357879 Opened 8 years ago Updated 2 years ago

What to do with extensions on the start of a Photon based browser

Categories

(Firefox :: General, enhancement, P3)

enhancement

Tracking

()

Firefox 57

People

(Reporter: andy+bugzilla, Unassigned)

References

(Depends on 1 open bug)

Details

This is a follow on from bug 1334662 and as per comment 11 is a seperate bug so we can discuss extensions without polluting that bug. When a Photon based browser starts, the non-WebExtension add-ons will be disabled as per the plan at https://wiki.mozilla.org/Add-ons/Firefox57. Will there be a notification to the user that add-ons have been disabled, what will that look like? In bug 1334662 I asked if the profile move over will include legacy extensions and we now feel it should, for the simple reason that some add-ons will likely update after 57. If an add-on updates to a WebExtensions, add-ons manager will still update the add-on (if disabled) and allow the end user to enable it and use the WebExtension version.
Whiteboard: [photon-onboarding]
Priority: -- → P2
Target Milestone: --- → Firefox 57
Whiteboard: [photon-onboarding] → [photon-onboarding][triage]
triage with dev team members. move priority to P3 till Product manager decide what exactly we want to show in the notification.
Flags: needinfo?(chsiang)
Priority: P2 → P3
Whiteboard: [photon-onboarding][triage] → [photon-onboarding]
sorry for my late response. Per my discussion with Markus, the addon team is working on their own plan to introduce the migration to web extension and how the user will be notified. There is no plan to bring that up during onboarding. Feel free to refer to this doc. https://docs.google.com/document/d/1wg-h4neJtDfwFj1XZf0Uo-wUUeS23JguLFOj-W5bALg/edit#
Flags: needinfo?(chsiang)
(In reply to Andy McKay [:andym] from comment #0) > Will there be a notification to the user that add-ons have been disabled, > what will that look like? We decided to not do a active notification, but only provide messaging in about:addons, for people that go looking for why their extension stopped working. So there will not be a clash in onboarding. Discussing how much notification is necessary to make people aware of missing extensions, or if it is necessary at all, we think that people using an extension will likely notice when it stopped working, so we will not need to provide a notification. In addition, any notification would likely cloud the 57 on-boarding experience with worries about extensions people might not even use, or have forgot about. We are still investigating if we need a different behavior for people that might risk their privacy or security when not notified. (People using a VPN, proxy or other anonymization tool that we might disable.)
Per the comment 2 and the comment 3, remove the [photon-onboarding] tag.
Whiteboard: [photon-onboarding]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.