Features/Desktop/Add-on hotfix: Difference between revisions

no edit summary
(Created page with "{{FeatureStatus |Feature name=Add-on Escape Valve |Feature stage=Draft |Feature version=Firefox 10 |Feature health=At risk |Feature status note=Currently in the engineering inves...")
 
No edit summary
Line 10: Line 10:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=Firefox should ship with a restartless by default. We could then issue updates to the add-on to ship stopgap fixes silently to all users.
|Feature open issues and risks=* General engineering spec
|Feature overview=Firefox should ship with a restartless installed by default. We could then issue updates to the add-on to ship stopgap fixes silently to users.
|Feature users and use cases=* We ship a new feature (like http:// hiding) and the user response is extremely negative. We issue an update to the add-on that flips a pref back to old behavior
|Feature users and use cases=* We ship a new feature (like http:// hiding) and the user response is extremely negative. We issue an update to the add-on that flips a pref back to old behavior
* We need to distrust a CA. We ship an update to the add-on that makes Firefox distrust it and users are silently updated within 24 hours
* We need to distrust a CA. We ship an update to the add-on that makes Firefox distrust it and users are silently updated within 24 hours
Line 18: Line 19:
* We know that Netflix/Hulu/etc does bad user sniffing for a particular Firefox version. We issue an update that drops down a infobar telling users what is happening and to contact the site, or we ship the add-on that changes the user agent on the site while they work on a fix
* We know that Netflix/Hulu/etc does bad user sniffing for a particular Firefox version. We issue an update that drops down a infobar telling users what is happening and to contact the site, or we ship the add-on that changes the user agent on the site while they work on a fix
* We want to speak directly to our users with a one-time marketing message / news flash. We ship an update to the add-on that pops up an infobar with the message and then never shows again
* We want to speak directly to our users with a one-time marketing message / news flash. We ship an update to the add-on that pops up an infobar with the message and then never shows again
|Feature requirements=* Must be hidden / users can't unistall
|Feature dependencies=* Leverages existing add-on manager
* Leverages existing add-on infrastructure
* AMO would see increased traffic, need to account for that
* RelEng would have to build it
* Need processes around creating a stopgap update
|Feature requirements=* Must be hidden / users can't uninstall
* Needs to be restartless but should support installing a new version that requires a restart
* Needs to be restartless but should support installing a new version that requires a restart
* Needs to happen at build time and be installed by every Firefox user
|Feature non-goals=* Ship new features to customers via add-ons
|Feature non-goals=* Ship new features to customers via add-ons
* Go to Firefox core with functionality broken into add-ons
* Go to Firefox core with functionality broken into add-ons
* Won't replace the need for software updates
* Won't replace the need for software updates
|Feature functional spec=* An add-on is created as part of a normal Firefox build and bundled
* The add-on cannot be uninstalled or disabled
* If the add-on is deleted / removed from the user profile it should be copied back
* The add-on will check AMO for updates
* The add-on will never uninstall itself
|Feature ux design=None required
|Feature implementation plan=* Investigate what it will take to hide an add-on securely (with no way to disable)
** In product? Whitelist
|Feature security review=Things to cover:
* How to make it so malicious add-ons can't use the same hiding mechanisms
* How to make it so malicious add-ons can't use the same uninstall prevention
Things already vetted:
* AMO webservices
* Add-on manager general functionality
|Feature privacy review=* Check with privacy team to see if add-ons give additional metrics by default we need to be aware of
* Before issuing an update get privacy team to sign off
|Feature localization review=* Should ship with all locales
* Shouldn't be any localization by default
* Need to discuss with the l10n team how we could localize if an update needed it
|Feature accessibility review=* Shouldn't impact accessibility
|Feature qa review=* QA needs to test the add-on is there
* QA needs to test the add-on works
* QA needs to test the add-on can't be uninstalled
}}
}}
{{FeatureInfo
{{FeatureInfo
canmove, Confirmed users
1,635

edits