Privacy/Features/Site-based data management UI

From MozillaWiki
Jump to navigation Jump to search
Feature Status ETA Owner
Site-based data management UI on track Q4 2011 Sid Stamm

Summary

It's helpful to be able to control what sites know and do on a site-by-site basis. Ideally, the site permissions dialog, cookie controls, and various other site-based preferences should be accessible via a single UI.

This feature will provide a UI in a content tab (much like the addons manager) that allows users to customize permissions and settings for sites on a site-by-site basis.

Team

Who's working on this?

  • Lead Developer: Margaret Leibovic
  • Product Manager:
  • QA:
  • UX: Jennifer Boriss
  • Security: Curtis Koenig
  • Privacy: Sid Stamm

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

  • We need to document existing data sources and mappings to the user interface
  • UI must be designed carefully, perhaps with a user study
  • Security and authenticity of the configuration UI must be verified and accessible to users.

Next Steps

Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.

  • [NEW] user study?
  • [NEW] design UX
  • [NEW] document data sources and mappings to UX
  • [NEW] security / privacy design discussion
  • [NEW] write patch
  • [NEW] test plan and tests
  • [NEW] land patch!

Related Bugs & Dependencies

Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.

  • There's a prototype patch in for site-specific privacy preferences in bug 573176
  • Need to create icons for the UI bug 587208

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

The site-based prefs will be implemented in content at an about page (about:permissions). It will be in-content (much like [about:addons]), and is intended to replace the various site-based or "all-sites" prefs and permissions that exist for:

  • cookies
  • passwords
  • geolocation permission
  • storage (IndexDB, localStorage)
  • add-on installation permission
  • pop-up blocking
  • image loading permission
  • HTTP Strict-Transport-Security setting
  • (history and bookmarks)? Maybe?

The UI will present a list of sites, searchable, ranked by frecency, complete with domain or subdomain name, site title, and favicon. When a user selects a site, the preferences for that site will be displayed, and the user will have the opportunity to change the preferences for that specific domain or subdomain.

The UI will include the ability to sites not yet accessed; this will provide pre-access preferences for those users who wish to block images from specific sites or assert control before it is needed.

Goals/Use Cases

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

  • Empower users to define data-sharing relationships with sites instead of with the various APIs in Firefox
  • Provide a secure, non-spoofable way to set these preferences.
  • Make it clear to users how they interact with each site (and all sites)
  • Assure users that the interface is part of Firefox and cannot be manipulated by a web site.

Non-Goals

Things we are specifically not doing or building as part of this feature.

  • This is not an enhancement of the site identity door-hanger (Larry)
  • This is not a new set of preferences or permissions, just a new interface to existing ones.
  • This is not a visualization of how people interact with sites
  • This is not in-flight configuration prompts or UX.

Other Documentation

Meeting Notes:

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked, but not yet at risk of missing this release.
  At Risk: feature is at risk of missing this release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.

Retrieved from "https://wiki.allizom.org/index.php?title=Privacy/Features/Site-based_data_management_UI&oldid=300963"