Features/Firefox/Blocklist UX enhancements

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.

Status

Blocklist UX enhancements [Plug-ins]
Stage Definition
Status `
Release target `
Health OK
Status note Initial planning. This has taken on some additional importance during the planning of response to BEAST+Java. I think we'll want to get this prioritized so we can have a tool we're less afraid to use and more confident will actually help. - Asa

Team

Product manager Kev Needham
Directly Responsible Individual Kev Needham
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Henrik Skupin
UX lead Jennifer Boriss
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Improve the user experience of dealing with blocklisted addons/plugins.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

  • Rewrite how the blocklist works functionally.

Stage 2: Design

5. Functional specification

Rough notes:

  • plugins - move dialog away from startup, only show when plugin is used
  • softblock - what does cancel do?

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

  • bug 406026 - Consider allowing the blocklist url to direct to a particular point in the blocklist

Stage 5: Release

10. Landing criteria

`


Feature details

Priority P2
Rank 11
Theme / Goal `
Roadmap Plugin Interactions
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-needed bug 744962
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `