Add-ons/Projects: Difference between revisions

1,149 bytes removed ,  18 October 2018
slight revision
(add caveat at the top about update frequency)
(slight revision)
Line 4: Line 4:


=== Mission-critical technical needs ===
=== Mission-critical technical needs ===
; <strike>Remove support for unpacked extensions
* Telemetry improvements
: The add-ons manager codebase currently support two separate code paths, one for unpacked and one for packed. This doubles the maintenance and testing burden, and unpacked, in particular, is prone to bugs and performance issues. It is no longer recommended on MDN. [targeting 62]
</strike>
 
; Telemetry improvements
: Telemetry of the add-ons manager (about:addons) and performance of addons is currently incomplete. [targeting 63 and 64]


=== New WebExtension APIs ===
=== New WebExtension APIs ===
Line 19: Line 14:
! API !! target release
! API !! target release
|-
|-
| UserScripts || 63
| UserScripts || 64
|-
|-
| topSites (places support) || 63
| declarativeContent || 65
|-
|-
| declarativeContent || 64
| Content handler API || TBD
|-
| Content handler API || 64
|-
| desktopCapture (analogous solution by WebRTC team) || TBD
|-
| Overlays || 65 (TBD)
|-
| Session management || (TBD)
|-
| Toolbars || (TBD)
|}
|}
* '''In discussion:''' color filter API
* '''Future:''' link to prioritized backlog (in progress)
* '''Future:''' link to long-term backlog (in progress)


=== Continuation of migration to Extensions ===
=== Continuation of migration to Extensions ===
Line 46: Line 27:
=== Security ===
=== Security ===
; Privacy Manifest Flags
; Privacy Manifest Flags
: We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed by the Add-on Manager. [targeting 63]
: We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed by the Add-on Manager. [target TBD]


=== Performance improvements ===
=== Performance improvements ===
; Storage.local backend change to indexedDB
; Storage.local backend change to indexedDB
: Improve performance and memory usage; also part of quantum flow. [targeting 63]
: Improve performance and memory usage; also part of quantum flow. [target TBD]


=== Engineering improvements ===
=== Engineering improvements ===
; Context menu improvements
; <strike>Context menu improvements
: Follow-on work for context menus and associated APIs. [targeting 63 and 64]
: Follow-on work for context menus and associated APIs.</strike>


; Resolve browser_style issues
; Resolve browser_style issues
: The browser_style manifest key is unclear in how it relates to built-in themes, user themes, and how maintenance should extend to add-ons requirements which may or may not be present in extensions.css. [targeting 64 and 65]
: The browser_style manifest key is unclear in how it relates to built-in themes, user themes, and how maintenance should extend to add-ons requirements which may or may not be present in extensions.css. [target TBD]


; Improve support for incognito
; Improve support for incognito
: There are outstanding issues with extensions, private browsing, and the incognito manifest key. [targeting 64 (and possibly 65)]
: There are outstanding issues with extensions, private browsing, and the incognito manifest key. [target TBD]
 
; Themes resolution
: The introduction of static themes and the Theming API introduce a host of UX issues on AMO and in Firefox that depend on a more concrete definition of "themes" and constraints to the Theming API. This affects both sides of Add-ons, the Visuals team, and community. [targeting 63-64]


; Delayed background startup pref'd on beyond Nightly
; <strike>Delayed background startup pref'd on beyond Nightly
: This fixes an issue with proxy and webRequest (at least), and results in extensions not needing to start during browser startup. [targeting 63]
: This fixes an issue with proxy and webRequest (at least), and results in extensions not needing to start during browser startup.</strike>


=== UX improvements ===
=== UX improvements ===
Line 78: Line 56:
=== Discoverability ===
=== Discoverability ===
; Feed desired extension that triggered install to /firstrun
; Feed desired extension that triggered install to /firstrun
: A substantial opportunity for add-on installation is to determine if a user installed Firefox from an AMO detail page. Add-ons users (whether new or pre-existing) retain at a higher rate than non-Add-ons users. [targeting 63 and 64]
: A substantial opportunity for add-on installation is to determine if a user installed Firefox from an AMO detail page. Add-ons users (whether new or pre-existing) retain at a higher rate than non-Add-ons users. [targeting 65]




Confirmed users
745

edits