In-content preferences

Please use "Edit with form" above to edit this page.

Status

In-content preferences
Stage	Development
Status	`
Release target	`
Health	OK
Status note	This feature will be worked on as a Spring 2012 course project for students at Michigan State University. Jared Wein and Blair McBride are the Mozilla points-of-contact for the project.

{{#set:Feature name=In-content preferences

|Feature stage=Development |Feature status=` |Feature version=` |Feature health=OK |Feature status note=This feature will be worked on as a Spring 2012 course project for students at Michigan State University. Jared Wein and Blair McBride are the Mozilla points-of-contact for the project. }}

Team

Product manager	Asa Dotzler
Directly Responsible Individual	Jared Wein
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	Mihaela Velimiroviciu
UX lead	Yuan Fang
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=Asa Dotzler

|Feature feature manager=Jared Wein |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Mihaela Velimiroviciu |Feature ux lead=Yuan Fang |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

Security and usability concerns associated with letting content area widgets modify the surrounding browser

Stage 1: Definition

1. Feature overview

As part of UX's goal to eliminate Firefox's separate management windows in favor of in-content designs, the Preferences window should be moved into the content area.

Such a move provides several benefits for users. First, it removes yet another easy-to-lose window. It means that changing preferences in Firefox can be an identical and easy experience across all devices, including tablet computers. It also means that more interactive portions of Preferences, such as about:permissions, can be integrated with the rest of preferences.

This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)

This project has two major components:

1. Move Preferences into in-content pages
2. Redesign Preferences such that their current usability problems are fixed and they integrate well within the content area

Goals:

1. Improve the design of Preferences
2. Integrate the parts of Firefox that should be in Preferences (such as the Add-ons Manager)
3. Move Preferences into the content area

2. Users & use cases

Modifying Firefox, using add-ons

3. Dependencies

`

4. Requirements

A fully-integrated, usable, redesigned Firefox Preferences which displays in the content area of the browser.

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

See these pages for mockups and designs of the new in-content preferences:

1. http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/
2. http://stephenhorlander.com/pages/incontent-ui-mockups/incontent-ui-mockups.html

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

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=Security and usability concerns associated with letting content area widgets modify the surrounding browser |Feature overview=As part of UX's goal to eliminate Firefox's separate management windows in favor of in-content designs, the Preferences window should be moved into the content area.

Such a move provides several benefits for users. First, it removes yet another easy-to-lose window. It means that changing preferences in Firefox can be an identical and easy experience across all devices, including tablet computers. It also means that more interactive portions of Preferences, such as about:permissions, can be integrated with the rest of preferences.

This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)

This project has two major components:

1. Move Preferences into in-content pages
2. Redesign Preferences such that their current usability problems are fixed and they integrate well within the content area

Goals:

1. Improve the design of Preferences
2. Integrate the parts of Firefox that should be in Preferences (such as the Add-ons Manager)
3. Move Preferences into the content area

|Feature users and use cases=Modifying Firefox, using add-ons |Feature dependencies=` |Feature requirements=A fully-integrated, usable, redesigned Firefox Preferences which displays in the content area of the browser. |Feature non-goals=` |Feature functional spec=` |Feature ux design=See these pages for mockups and designs of the new in-content preferences:

1. http://blog.stephenhorlander.com/2010/06/in-content-ui-visual-unification/
2. http://stephenhorlander.com/pages/incontent-ui-mockups/incontent-ui-mockups.html

|Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority	P3
Rank	999
Theme / Goal	`
Roadmap	User Experience
Secondary roadmap	`
Feature list	Desktop
Project	`
Engineering team	Desktop front-end

{{#set:Feature priority=P3

|Feature rank=999 |Feature theme=` |Feature roadmap=User Experience |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}