Add-ons/Projects/Jazz: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (retirement message)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''UPDATE: this project has been retired as of Sep 2018'''
An effort to make it clear to users the ways in which extensions change the behavior of their browser.
An effort to make it clear to users the ways in which extensions change the behavior of their browser.


Line 21: Line 23:
== Milestones ==
== Milestones ==


What's been done so far:
The best way to see what's landed, apart from bugs, is in the [https://trello.com/b/PC9kB14s/webextensions?menu=filter&filter=label:Jazz%20%F0%9F%91%8B trello board, filtered down].
 
...


== Bugs ==
== Bugs ==
Line 38: Line 38:
}
}
</bugzilla>
</bugzilla>
=== Trello cards ===
These may or may not be visible to everyone:
* [https://trello.com/c/vnubkZjY/148-extension-setting-home-page-or-newtab Extension setting Home Page &/or newTab]
* [https://trello.com/c/0LGSpfz6/157-user-interface-for-exposing-how-extensions-change-firefox User interface for exposing how extensions change Firefox]
=== Mocks ===
The current mocks can be found at https://mozilla.invisionapp.com/share/6HCITJKP8.

Latest revision as of 04:12, 21 September 2018

UPDATE: this project has been retired as of Sep 2018

An effort to make it clear to users the ways in which extensions change the behavior of their browser.

Note from andym: I hate giving projects code names, but we couldn't think of a good summary for this project that didn't involve being confused with every other permissions and objects project. So we have Jazz and that seems cool since we have Disco Pane.

Project Jazz

Let's find a way to show users of extensions what the extensions do to their browser after they are installed. This includes, but is not limited to:

  • showing a user the permissions granted by a user to the add-on
  • allow a user to revoke optional permissions from the add-on
  • showing a user which command combinations an add-on requests
  • allowing a user to change the command combinations an add-on requests
  • show what collisions in APIs add-ons might represent
  • allowing the user to override or change key functionality such as: search engines, home page, new tab pages
    • we need this for *all* prefs that are accessible via the UI and also controllable by WebExtensions
    • we need to consider whether a user should be able to specify a value for a preference, and have that block WebExtensions from overriding the preference, and if so, how would that work/what would it look like

Milestones

The best way to see what's landed, apart from bugs, is in the trello board, filtered down.

Bugs

Tracking bug

Tracking bug is 1342584.

Bugzilla query error

Array ( [type] => error [message] => http-timed-out [params] => Array ( [0] => https://bugzilla.mozilla.org/bzapi/bug?blocks=1342584&include_fields=id&include_fields=priority&include_fields=status&include_fields=summary&status=UNCONFIRMED&status=ASSIGNED&status=NEW&status=REOPENED ) ) 1