Confirmed users
1,041
edits
Extension Blocklisting: Difference between revisions
Jump to navigation
Jump to search
→Use Cases
| Line 43: | Line 43: | ||
== Use Cases == | == Use Cases == | ||
The following has been identified as potential use cases for blocklisting extensions: | |||
* extensions that break the application | |||
* extensions that have security vulnerabilities | |||
* extensions that crash the application | |||
* extensions that advertise a <tt>targetApplication</tt> for a future release that break the future release | |||
* extensions that have memory leaks that adversely affect the performance of the application | |||
* malicious extensions that have an identifiable id (e.g. an id that doesn't change) | |||
Several of these terms are purposefully subjective and will be defined as the process for managing the blocklist is developed. | |||
== Functional Requirements == | == Functional Requirements == | ||